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
Hello,
We are not able to understand why the default value is 0.2d in ZoneAwareLoadBalancer
triggeringLoad = DynamicPropertyFactory.getInstance().getDoubleProperty(
"ZoneAwareNIWSDiscoveryLoadBalancer." + this.getName() + ".triggeringLoadPerServerThreshold", 0.2d);
in our environment all the servers have load of Integer 2,3 ,5
The calculation is:
loadPerServer = ((double) activeConnectionsCountOnAvailableServer) / (instanceCount - circuitBreakerTrippedCount);
assume that we have 1 instance and circuit is 1 and we have few connection at any moment it means that our loadPerServer will be much bigger than 0.2
Do we miss anything ?
We don't want to filter those zone with this low load ?
Any hint will help us.
Also we have tens of services and we don't want to change the value for each one of them.
Can the code be change that the default will be globally
The text was updated successfully, but these errors were encountered:
Hello,
We are not able to understand why the default value is 0.2d in ZoneAwareLoadBalancer
triggeringLoad = DynamicPropertyFactory.getInstance().getDoubleProperty(
"ZoneAwareNIWSDiscoveryLoadBalancer." + this.getName() + ".triggeringLoadPerServerThreshold", 0.2d);
in our environment all the servers have load of Integer 2,3 ,5
The calculation is:
loadPerServer = ((double) activeConnectionsCountOnAvailableServer) / (instanceCount - circuitBreakerTrippedCount);
assume that we have 1 instance and circuit is 1 and we have few connection at any moment it means that our loadPerServer will be much bigger than 0.2
Do we miss anything ?
We don't want to filter those zone with this low load ?
Any hint will help us.
Also we have tens of services and we don't want to change the value for each one of them.
Can the code be change that the default will be globally
The text was updated successfully, but these errors were encountered: