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
considering 1 situation:
when one graph shutdown, then sessions connected to this graph will reconnect to others. if session pool is never updated, this graph will never be used although it maybe be recovered lately. and this case is regular when upgrading graph.
if this is true, maybe we should enhance the load balancer in session pool or connection pool. for example, we can build a map with key=address, val=sessions to it, define min/max session size to each address and then update session to each address timely?
The text was updated successfully, but these errors were encountered:
considering 1 situation:
when one graph shutdown, then sessions connected to this graph will reconnect to others. if session pool is never updated, this graph will never be used although it maybe be recovered lately. and this case is regular when upgrading graph.
if this is true, maybe we should enhance the load balancer in session pool or connection pool. for example, we can build a map with key=address, val=sessions to it, define min/max session size to each address and then update session to each address timely?
The text was updated successfully, but these errors were encountered: