[jira] [Updated] (IGNITE-11745) Rebalancing overwhelmingly prefers some supplier nodes to others
[ https://issues.apache.org/jira/browse/IGNITE-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-11745: - Ignite Flags: (was: Docs Required) > Rebalancing overwhelmingly prefers some supplier nodes to others > > > Key: IGNITE-11745 > URL: https://issues.apache.org/jira/browse/IGNITE-11745 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Critical > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > When cache has backups, and you add third node to cluster, Ignite will only > rebalance data from single node. > When you add n-th node, Ignite will not rebalance from some nodes and it will > pull 10x as much data from some nodes than from others. > This is because we filter static nodes list by partition availability and > then pick the first one. Overwhelmingly it is the first nodes in list and > nodes towards the end of list will never get to supply partitions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11745) Rebalancing overwhelmingly prefers some supplier nodes to others
[ https://issues.apache.org/jira/browse/IGNITE-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Goncharuk updated IGNITE-11745: -- Fix Version/s: 2.8 > Rebalancing overwhelmingly prefers some supplier nodes to others > > > Key: IGNITE-11745 > URL: https://issues.apache.org/jira/browse/IGNITE-11745 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Critical > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > When cache has backups, and you add third node to cluster, Ignite will only > rebalance data from single node. > When you add n-th node, Ignite will not rebalance from some nodes and it will > pull 10x as much data from some nodes than from others. > This is because we filter static nodes list by partition availability and > then pick the first one. Overwhelmingly it is the first nodes in list and > nodes towards the end of list will never get to supply partitions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11745) Rebalancing overwhelmingly prefers some supplier nodes to others
[ https://issues.apache.org/jira/browse/IGNITE-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Kasnacheev updated IGNITE-11745: - Ignite Flags: Docs Required > Rebalancing overwhelmingly prefers some supplier nodes to others > > > Key: IGNITE-11745 > URL: https://issues.apache.org/jira/browse/IGNITE-11745 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Critical > Time Spent: 10m > Remaining Estimate: 0h > > When cache has backups, and you add third node to cluster, Ignite will only > rebalance data from single node. > When you add n-th node, Ignite will not rebalance from some nodes and it will > pull 10x as much data from some nodes than from others. > This is because we filter static nodes list by partition availability and > then pick the first one. Overwhelmingly it is the first nodes in list and > nodes towards the end of list will never get to supply partitions. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
