Closed fighterhit closed 1 month ago
I found that _request_timeout
can be passed as a parameter to watch.Watch().stream
according to #259, which finally used as the timeout
parameter of aiohttp (default 5min), which can avoid TimeoutError
, but another exception(Reason: Expired: too old resource version
...) will still be thrown after the _request_timeout
is reached, but at least we can increase the watch time.
Duplicated of #136
If you want to watch forever it should work without _request_timeout
, timeout
. These 410s are real problem here.
Duplicated of #136
If you want to watch forever it should work without
_request_timeout
,timeout
. These 410s are real problem here.
@tomplus Thanks, is there a solution now?
Not now, but I'll take a look on it next week
In order to do
service discovery
in my self-hosted k8s cluster, I use the following code to watch the changes of theendpoint
under the specified namespace, but it will exit with the following exception after a period of time. What is the reason? I found that it takes about 5 minutes from startup to abnormal exit. Is this related to thetimeout_seconds
setting? But according to the cause of the exception, it doesn't seem so, and I think thewatch
operation should keep observing the changes of the endpoint by default.When I set
timeout_seconds=600
, the program still exits 5 minutes after startup, but another exception is raised.