[IGNITE-14228] Ducktape test of rebalance for in-memory mode

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: IEP-56
• Sprint: Ducktape Sprint 4, Ducktape Sprint 5, Ducktape Sprint 6, Ducktape Sprint 7
• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Dmitriy Sorokin
• Reporter: Dmitriy Sorokin
• Created: 24/Feb/21 11:38
• Updated: 02/Apr/21 06:03
• Resolved: 16/Mar/21 07:58

Description

This test should check the rebalance on in-memory caches in basic scenario: rebalance triggered by two event types: node join and node left the topology.
The test should be able to run on large amounts of data enough to ensure rebalancing time about of several minutes.

Test parameters:

1. Initial node count (derived from test context);
2. Cache count - the count of caches to create and data preload;
3. Cache entry count - the count of entries per cache to preload;
4. Cache entry size - the size of each cache entry in bytes;
5. Rebalance thread pool size - the value for IgniteConfiguration#rebalanceThreadPoolSize property (see configuring rebalance thread pool title), expected that greater value makes rebalance faster.
6. Rebalance batch size - the value for IgniteConfiguration#rebalanceBatchSize property (see other rebalance properties), expected that greater value makes rebalance faster on large data or throttling enabled (rebalanceThrottling > 0).
7. Rebalance throttle - the value for IgniteConfiguration#rebalanceThrottle property (see rebalance message throttling, other rebalance properties), 0 - throttling disabled, greater value makes rebalance slower.

Test result: time taken to rebalance process.

Issue Links

• links to: GitHub Pull Request #8832