-
-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adjustable T1, T2 and T4 timeouts #47
Comments
I would not go with this func. I would still like to know some use case of changing this values from default one? |
T1 is an estimate of RTT and it should be quite different when you connect to a node in the same data center or to a node on another continent. In the former case it should retry (and eventually fail and do failover) much earlier. It's not that important for my current project, where I'm trying to go with
Yeah, it doesn't look nice. I just can't come up with a better way now. Maybe, introducing more |
thnx for sharing. Sure T1 is most important. So it is more I want to change T1 and let others be populated. Maybe we can have this to be populated on package level Let me know would this be enough. We can always export all timers, but maybe for now keeping package API small? |
This waits too long. Adding priority |
@a12n was delayed, but done. |
These are constants now and can't be changed.
Probably, the values should be per client/server or per transaction. In the simplest case, they just can be made
var
. This would allow to change the values at startup. Something like this:The drawback here is the changed type of
Timer_*
, the values have to be functions on T1 and T4. Although the values are used only insidetransaction
package insipgo
they're still exported and available for external code.Maybe, you have a better idea on making the timers configurable?
The text was updated successfully, but these errors were encountered: