You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One would assume that setting -ingester.ingester.max-transfer-retries to zero disables transfers, when in fact it enables infinite number of retries instead. This should either be documented or fixed.
Reason for this behaviour is that -ingester.ingester.max-transfer-retries value is passed as MaxRetries in BackOffConfig struct, where zero means infinite retries.
The text was updated successfully, but these errors were encountered:
pstibrany
added a commit
to grafana/cortex
that referenced
this issue
Nov 4, 2019
…disabled.
Due to interaction with BackOffConfig.MaxRetries, zero value meant infinite number
of attempts, which is hardly ever a desired behaviour (with no ingester waiting to
accept a transfer, this would never end).
Fixedcortexproject#1771.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
#1777)
* If ingester.max-transfer-retries is set to 0, hand-over attempts are disabled.
Due to interaction with BackOffConfig.MaxRetries, zero value meant infinite number
of attempts, which is hardly ever a desired behaviour (with no ingester waiting to
accept a transfer, this would never end).
Fixed#1771.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
* Fixed typo
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
* Fix ingester.max-transfer-retries argument name.
Signed-off-by: Peter Štibraný <peter.stibrany@grafana.com>
One would assume that setting
-ingester.ingester.max-transfer-retries
to zero disables transfers, when in fact it enables infinite number of retries instead. This should either be documented or fixed.Reason for this behaviour is that -ingester.ingester.max-transfer-retries value is passed as
MaxRetries
inBackOffConfig
struct, where zero means infinite retries.The text was updated successfully, but these errors were encountered: