-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Old WebSockets are not explicitly closed on HTTP_GONE #3186
Milestone
Comments
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
May 31, 2021
…ions and closure this localizes the state of a websocket to the listener, rather than the runner to have a clearer lifecycle. it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
May 31, 2021
…ions and closure this localizes the state of a websocket to the listener, rather than the runner to have a clearer lifecycle. it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
May 31, 2021
…ions and closure this localizes the state of a websocket to the listener, rather than the runner to have a clearer lifecycle. it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
May 31, 2021
…ions and closure this localizes the state of a websocket to the listener, rather than the runner to have a clearer lifecycle. it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
May 31, 2021
…ions and closure this localizes the state of a websocket to the listener, rather than the runner to have a clearer lifecycle. it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 2, 2021
…ions and closure this localizes the state of a websocket to the listener, rather than the runner to have a clearer lifecycle. it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 2, 2021
…ions and closure this localizes the state of a websocket to the listener, rather than the runner to have a clearer lifecycle. it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 2, 2021
…ions and closure this localizes the state of a websocket to the listener, rather than the runner to have a clearer lifecycle. it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 3, 2021
…ions and closure this localizes the state of a websocket to the listener and removes the runner abstraction it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 3, 2021
…ions and closure this localizes the state of a websocket to the listener and removes the runner abstraction it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 3, 2021
…ions and closure this removes the runner abstraction it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 8, 2021
…ions and closure this removes the runner abstraction it also replaces the use of BlockingQueue with CompletableFuture.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jun 8, 2021
…ions and closure this removes the runner abstraction it also replaces the use of BlockingQueue with CompletableFuture.
manusa
pushed a commit
that referenced
this issue
Jun 9, 2021
this removes the runner abstraction it also replaces the use of BlockingQueue with CompletableFuture.
Closed via #3197 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The expectation in the code seems to be that on HTTP_GONE the api server will kill the websocket connection:
kubernetes-client/kubernetes-client/src/main/java/io/fabric8/kubernetes/client/dsl/internal/WatchConnectionManager.java
Line 100 in 74cc63d
However we have a log / threaddump confirming a lingering websocket 2 hours after that event. Is there a reference for that expected behavior and/or could there be some logic to quietly close the websocket at this point?
cc @manusa @rohanKanojia
The text was updated successfully, but these errors were encountered: