Watchers time out after 100 seconds

[qmfrederik]

• The default timeout for the HttpClient is 100 seconds, so the watchers will timeout after this amount of time.
• There is no default API to override the timeout on a per-request basis
• https://www.thomaslevesque.com/2018/02/25/better-timeout-handling-with-httpclient/ describes an alternative but it implies setting the timeout to Infinite for all requests and then specifying the timeout on a per-request basis for all requests.

[qmfrederik]

I'm not entirely sure, but this appears to be an issue when the server does not send any content at all in the first 100 seconds after the GET request is issued. When the server does send a first response, and subsequent updates come in intervals greater than 100 seconds, the code appears to work fine.

[brendandburns]

@qmfrederik is there an action we can take here? Or is this to document the issue for people who encounter it?

[qmfrederik]

We could implement the approach described here, which allows us to set a timeout on a per-request level, but that would require updating the generator, so it's not a trivial fix.

Alternatively the watchers can catch timeout exceptions and try again.

I encountered it and for now have try/catch in my calling code. I'm not very happy with that and may want to revisit it in the future, and this issue mainly acts as a reminder to myself/documentation to others 😄 .

[fejta-bot]

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

[fejta-bot]

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

[fejta-bot]

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

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.
/close

Instructions 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.