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
We were supposed to add this a long time ago, but we never have.
Because realtime sources connect to sinks via a simple shuffled list of IPs, if more nodes are added to the other cluster (or if clusters are offline and then brought back online) the realtime connections are never rebalanced fairly to avoid overloading sink nodes.
Given that we know the list of IPs in the other cluster, this should not be that hard, each sink node should have at least N div M realtime connections and N rem M nodes should have one additional connection. If this is not true, kill some realtime connections and let them re-establish. We can periodically do this check, say every 5 minutes or so?
The text was updated successfully, but these errors were encountered:
Basho-JIRA
changed the title
Rebalance realtime connections to be fair to the sink
Rebalance realtime connections to be fair to the sink [JIRA: RIAK-2708]
Jul 22, 2016
We were supposed to add this a long time ago, but we never have.
Because realtime sources connect to sinks via a simple shuffled list of IPs, if more nodes are added to the other cluster (or if clusters are offline and then brought back online) the realtime connections are never rebalanced fairly to avoid overloading sink nodes.
Given that we know the list of IPs in the other cluster, this should not be that hard, each sink node should have at least N div M realtime connections and N rem M nodes should have one additional connection. If this is not true, kill some realtime connections and let them re-establish. We can periodically do this check, say every 5 minutes or so?
The text was updated successfully, but these errors were encountered: