mirror of
https://github.com/kemko/nomad.git
synced 2026-01-01 16:05:42 +03:00
5d09d7ad07
When a blocking query on the client hits a retryable error, we change the max query time so that it falls within the `RPCHoldTimeout` timeout. But when the retry succeeds we don't reset it to the original value. Because the calls to `Node.GetClientAllocs` reuse the same request struct instead of reallocating it, any retry will cause the agent to poll at a faster frequency until the agent restarts. No other current RPC on the client has this behavior, but we'll fix this in the `rpc` method rather than in the caller so that any future users of the `rpc` method don't have to remember this detail. Fixes: https://github.com/hashicorp/nomad/issues/25033
4 lines
135 B
Plaintext
4 lines
135 B
Plaintext
```release-note:bug
|
|
client: Fixed a bug where temporary RPC errors cause the client to poll for changes more frequently thereafter
|
|
```
|