[jira] [Updated] (IGNITE-8415) Manual cache().rebalance() invocation may cancel currently running rebalance
[ https://issues.apache.org/jira/browse/IGNITE-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-8415: Fix Version/s: (was: 2.10) > Manual cache().rebalance() invocation may cancel currently running rebalance > > > Key: IGNITE-8415 > URL: https://issues.apache.org/jira/browse/IGNITE-8415 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Priority: Major > > If historical rebalance happens and during this process we manually invoke > {noformat} > Ignite.cache(CACHE_NAME).rebalance().get(); > {noformat} > then currently running rebalance will be cancelled and started new which > seems not right way. Moreover, after new rebalance finish we can lost some > data in case of rebalancing entry removes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8415) Manual cache().rebalance() invocation may cancel currently running rebalance
[ https://issues.apache.org/jira/browse/IGNITE-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksey Plekhanov updated IGNITE-8415: -- Fix Version/s: (was: 2.9) 2.10 > Manual cache().rebalance() invocation may cancel currently running rebalance > > > Key: IGNITE-8415 > URL: https://issues.apache.org/jira/browse/IGNITE-8415 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Priority: Major > Fix For: 2.10 > > > If historical rebalance happens and during this process we manually invoke > {noformat} > Ignite.cache(CACHE_NAME).rebalance().get(); > {noformat} > then currently running rebalance will be cancelled and started new which > seems not right way. Moreover, after new rebalance finish we can lost some > data in case of rebalancing entry removes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8415) Manual cache().rebalance() invocation may cancel currently running rebalance
[ https://issues.apache.org/jira/browse/IGNITE-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Maxim Muzafarov updated IGNITE-8415: Fix Version/s: (was: 2.8) 2.9 > Manual cache().rebalance() invocation may cancel currently running rebalance > > > Key: IGNITE-8415 > URL: https://issues.apache.org/jira/browse/IGNITE-8415 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Priority: Major > Fix For: 2.9 > > > If historical rebalance happens and during this process we manually invoke > {noformat} > Ignite.cache(CACHE_NAME).rebalance().get(); > {noformat} > then currently running rebalance will be cancelled and started new which > seems not right way. Moreover, after new rebalance finish we can lost some > data in case of rebalancing entry removes. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-8415) Manual cache().rebalance() invocation may cancel currently running rebalance
[ https://issues.apache.org/jira/browse/IGNITE-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pavel Kovalenko updated IGNITE-8415: Fix Version/s: (was: 2.7) 2.8 > Manual cache().rebalance() invocation may cancel currently running rebalance > > > Key: IGNITE-8415 > URL: https://issues.apache.org/jira/browse/IGNITE-8415 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Priority: Major > Fix For: 2.8 > > > If historical rebalance happens and during this process we manually invoke > {noformat} > Ignite.cache(CACHE_NAME).rebalance().get(); > {noformat} > then currently running rebalance will be cancelled and started new which > seems not right way. Moreover, after new rebalance finish we can lost some > data in case of rebalancing entry removes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-8415) Manual cache().rebalance() invocation may cancel currently running rebalance
[ https://issues.apache.org/jira/browse/IGNITE-8415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-8415: --- Fix Version/s: (was: 2.6) 2.7 > Manual cache().rebalance() invocation may cancel currently running rebalance > > > Key: IGNITE-8415 > URL: https://issues.apache.org/jira/browse/IGNITE-8415 > Project: Ignite > Issue Type: Bug > Components: cache >Affects Versions: 2.4 >Reporter: Pavel Kovalenko >Priority: Major > Fix For: 2.7 > > > If historical rebalance happens and during this process we manually invoke > {noformat} > Ignite.cache(CACHE_NAME).rebalance().get(); > {noformat} > then currently running rebalance will be cancelled and started new which > seems not right way. Moreover, after new rebalance finish we can lost some > data in case of rebalancing entry removes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)