Hello,
I am running into an issue where all of my indexers are timing out due to a intermittent poor internet connection. This ultimately leaves them being unavailable for a period of up to 24hrs (this is my understanding from reading the help guides). Is there a way to configure any of these parameters? For example how many checks must fail before the indexer is considered temporarily dead and when it is considered dead how long the retry intervals are?
Thanks for the assistance.
No it is not customizable we have no plans to do so, but the backup is incremental and applies to constitutive failures, if there are successful responses the next interval is reduced.
Is there a reason why this can’t be user defined? it seems to be a basic thing. It really creates an issue if using poor connection or VPN for example and the tunnel goes down periodically. The back off timing just creates an issue.
Changing the backoff isn’t a solution to a poor network connection and the backoff could be applied from the indexer, not a failing connection.
Depending how the connection is failing we may be able to prevent it from backing off, but we’ll need to see ((trace logs)) of the failing connections to see if that’s possible.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.