Ilya Lantukh created IGNITE-7592: ------------------------------------ Summary: 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
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 awaitPartitionMapExchange(), though probability that it will happen is rather low (<10%). -- This message was sent by Atlassian JIRA (v7.6.3#76005)