What does this error mean: The last watch has yet to terminate as expected, will force start another watch. #6887
-
|
I'm seeing the error message below in our logs, I'm not sure what it means. Can someone explain? Context: we use |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
The logic is hesitant about starting additional watches because there can be resource issues with too many concurrent watches. Under normal circumstances, the closing of a websocket is bi-directional. On side sends a close, then the other sends back a close. The kuberentes client logic here is expecting that the server will have acknowledged the close, but it hasn't. It's possible this could happen for a benign reason, such as the api server becomes unreachable after the close attempt. If this keeps happening we'll need to see more of a log to determine the full sequence of events. For now if the watches recover, then there's no need to worry. |
Beta Was this translation helpful? Give feedback.
The logic is hesitant about starting additional watches because there can be resource issues with too many concurrent watches. Under normal circumstances, the closing of a websocket is bi-directional. On side sends a close, then the other sends back a close. The kuberentes client logic here is expecting that the server will have acknowledged the close, but it hasn't. It's possible this could happen for a benign reason, such as the api server becomes unreachable after the close attempt. If this keeps happening we'll need to see more of a log to determine the full sequence of events. For now if the watches recover, then there's no need to worry.