[jira] [Updated] (IGNITE-14226) Ducktape test of rebalance
[ https://issues.apache.org/jira/browse/IGNITE-14226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anton Vinogradov updated IGNITE-14226: -- Sprint: Ducktape Sprint 4, Ducktape Sprint 5 (was: Ducktape Sprint 4) > Ducktape test of rebalance > -- > > Key: IGNITE-14226 > URL: https://issues.apache.org/jira/browse/IGNITE-14226 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Sorokin >Assignee: Dmitriy Sorokin >Priority: Major > > The test should check the rebalance on both in-memory caches and persistent > caches. > In case of persistent caches, the test also should check both modes of > rebalance: full and historical (asserts is needed that the proper mode of > rebalance was worked). > Basic scenario: > Testing of rebalance triggered by two event types: node enter and node leave > (baseline change in persistent mode). > Extended scenario: > Node entering or leaving during rebalance process. > Test parameters: > # Initial node count; > # Cache count; > # Cache entry count; > # Cache entry size; > # Mode: in-memory or persistence; > # Rebalance trigger event: node enter or node leave. > Test result: time taken to rebalance process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14226) Ducktape test of rebalance
[ https://issues.apache.org/jira/browse/IGNITE-14226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Sorokin updated IGNITE-14226: - Description: The test should check the rebalance on both in-memory caches and persistent caches. In case of persistent caches, the test also should check both modes of rebalance: full and historical (asserts is needed that the proper mode of rebalance was worked). Basic scenario: Testing of rebalance triggered by two event types: node enter and node leave (baseline change in persistent mode). Extended scenario: Node entering or leaving during rebalance process. Test parameters: # Initial node count; # Cache count; # Cache entry count; # Cache entry size; # Mode: in-memory or persistence; # Rebalance trigger event: node enter or node leave. Test result: time taken to rebalance process. was: The test should check the rebalance on both in-memory caches and persistent caches. In case of persistent caches, the test also should check both modes of rebalance: full and the historical (asserts is needed that the proper mode of rebalance was worked). Basic scenario: Testing of rebalance triggered by two event types: node enter and node leave (baseline change if persistent mode). Extended scenario: Node entering or leaving during rebalance process. Test parameters: # Initial node count; # Cache count; # Cache entry count; # Cache entry size; # Mode: in-memory or persistence; # Rebalance trigger event: node enter or node leave. Test result: time taken to rebalance process. > Ducktape test of rebalance > -- > > Key: IGNITE-14226 > URL: https://issues.apache.org/jira/browse/IGNITE-14226 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Sorokin >Assignee: Dmitriy Sorokin >Priority: Major > > The test should check the rebalance on both in-memory caches and persistent > caches. > In case of persistent caches, the test also should check both modes of > rebalance: full and historical (asserts is needed that the proper mode of > rebalance was worked). > Basic scenario: > Testing of rebalance triggered by two event types: node enter and node leave > (baseline change in persistent mode). > Extended scenario: > Node entering or leaving during rebalance process. > Test parameters: > # Initial node count; > # Cache count; > # Cache entry count; > # Cache entry size; > # Mode: in-memory or persistence; > # Rebalance trigger event: node enter or node leave. > Test result: time taken to rebalance process. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14226) Ducktape test of rebalance
[ https://issues.apache.org/jira/browse/IGNITE-14226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Sorokin updated IGNITE-14226: - Sprint: Ducktape Sprint 4 > Ducktape test of rebalance > -- > > Key: IGNITE-14226 > URL: https://issues.apache.org/jira/browse/IGNITE-14226 > Project: Ignite > Issue Type: Test >Reporter: Dmitriy Sorokin >Assignee: Dmitriy Sorokin >Priority: Major > > The test should check the rebalance on both in-memory caches and persistent > caches. > In case of persistent caches, the test also should check both modes of > rebalance: full and the historical (asserts is needed that the proper mode of > rebalance was worked). > Basic scenario: > Testing of rebalance triggered by two event types: node enter and node leave > (baseline change if persistent mode). > Extended scenario: > Node entering or leaving during rebalance process. > Test parameters: > # Initial node count; > # Cache count; > # Cache entry count; > # Cache entry size; > # Mode: in-memory or persistence; > # Rebalance trigger event: node enter or node leave. > Test result: time taken to rebalance process. -- This message was sent by Atlassian Jira (v8.3.4#803005)