[ https://issues.apache.org/jira/browse/IGNITE-7592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dmitriy Pavlov updated IGNITE-7592: ----------------------------------- Fix Version/s: (was: 2.6) 2.7 > Dynamic cache with rebalanceDelay == -1 doesn't trigger late affinity > assignment even after explicit rebalance is called on every node > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: IGNITE-7592 > URL: https://issues.apache.org/jira/browse/IGNITE-7592 > Project: Ignite > Issue Type: Bug > Affects Versions: 2.4 > Reporter: Ilya Lantukh > Assignee: Maxim Muzafarov > Priority: Major > Fix For: 2.7 > > > Reproducer: > {noformat} > startGrids(NODE_COUNT); > IgniteEx ig = grid(0); > ig.cluster().active(true); > awaitPartitionMapExchange(); > IgniteCache<Integer, Integer> cache = > ig.createCache( > new CacheConfiguration<Integer, Integer>() > .setName(CACHE_NAME) > .setCacheMode(PARTITIONED) > .setBackups(1) > .setPartitionLossPolicy(READ_ONLY_SAFE) > .setReadFromBackup(true) > .setWriteSynchronizationMode(FULL_SYNC) > .setRebalanceDelay(-1) > ); > for (int i = 0; i < NODE_COUNT; i++) > grid(i).cache(CACHE_NAME).rebalance().get(); > awaitPartitionMapExchange(); > {noformat} > Sometimes this code will hang on the last awaitPartitionMapExchange(), though > probability that it will happen is rather low (<10%). -- This message was sent by Atlassian JIRA (v7.6.3#76005)