jvarenina edited a comment on pull request #7378:
URL: https://github.com/apache/geode/pull/7378#issuecomment-1048513322


   Hi reviewers,
   
   With this solution each server will now send CacheServerLoadMessage 
containing the correct connection load of the gateway-receiver to all locators 
in cluster. This will happen every 5 seconds as configured with 
load-poll-interval parameter. Additionally, coordinator locator will on its own 
increase the load each time it provides the server location to remote 
gateway-sender in ClientConnectionRequest/ClientConnectionResponse. Locator 
only maintains load temporarily until CacheServerLoadMessage is received. This 
makes sense as the load that server tracks is more accurate than the load 
tracked by locator. Locator only increase load based on the received connection 
requests while server adjusts the load each time connection is actually 
established and disconnected.
   
   When gateway-sender connections are establishing due to traffic, then 
usually ClientConnectionRequest are sent to coordinator (locator) in bursts. 
This will result with the load on locator that is way ahead of the server load, 
because servers did not established those connections yet. If during these 
bursts CacheServerLoadMessage message come to locator carrying low load value 
for one of the gateway-receivers, then that receiver will be picked more 
frequently (will have lowest load), and that could result with unbalanced 
gateway-sender connections. In order for this to have a big impact on 
load-balancing of sender connections the gateway-receivers must be started with 
some small delay, so that CacheServerLoadMessages are sent with some delay that 
is enough to cause imbalance. If CacheServerLoadMessages were sent at the 
similar time then this would not be a problem as all messages would have 
similar load and would update locator at similar time.
   
   I would be really grateful if you could share your opinion on this matter? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@geode.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to