Repository navigation
IncompleteRead error while streaming to watch some apis #540
Description
Activity
- changed the title
[-]I got and error while streaming to watch some apis[/-][+]I got an error while streaming to watch some apis[/+]on May 25, 2018 - changed the title
[-]I got an error while streaming to watch some apis[/-][+]I got IncompleteRead error while streaming to watch some apis[/+]on May 25, 2018 - changed the title
[-]I got IncompleteRead error while streaming to watch some apis[/-][+]IncompleteRead error while streaming to watch some apis[/+]on May 29, 2018 I had issues with Watch() while using k8 v1.7 and python client 6.0. Later I changed python client to 2.0 and it's working. What I observed is that the client documentation is not updated for the latest version which 6.0.
Now.. I'm doing like this.
from urllib3.exceptions import ProtocolError ... w = watch.Watch() try: for event in w.stream(list_resources, **kwargs): ... except ProtocolError: print('skip this error... because kubelet disconnect client after default 10m...') ...
Is it a known exception? then I will close the issue...
Issues go stale after 90d of inactivity.
Mark the issue as fresh with/remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale- addedlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
on Apr 24, 2019 Stale issues rot after 30d of inactivity.
Mark the issue as fresh with/remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.If this issue is safe to close now please do so with
/close.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten- addedlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.and removedlifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.Denotes an issue or PR has remained open with no activity and has become stale.
on May 24, 2019 Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close@fejta-bot: Closing this issue.
Details
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/closeInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
- added a commit that references this issue
on Aug 16, 2019
I'm using 6.0.0 with Kubernetes 1.9.
I'm trying using watch API like this.
At first loop, it works fine.
However, I got this error from the second loop when there is no change of watching Resources.
I think it's because k8s disconnects watch api after 10 minutes.
kubernetes-client intentionally let me handle this?