[jira] [Updated] (IGNITE-14477) Ducktape test of rebalance for persistent mode
[
https://issues.apache.org/jira/browse/IGNITE-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Daschinsky updated IGNITE-14477:
-
Ignite Flags: (was: Docs Required,Release Notes Required)
> Ducktape test of rebalance for persistent mode
> --
>
> Key: IGNITE-14477
> URL: https://issues.apache.org/jira/browse/IGNITE-14477
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Sorokin
>Assignee: Sergei Ryzhov
>Priority: Major
> Labels: IEP-56
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> This test should check the rebalance on persistent caches in two scenarios:
> # Full rebalance which triggered by two event types: node join and node left
> the topology (need to update baseline topology).
> # Historical rebalance which triggered by joining to cluster of missed node
> with existing PDS:
> ** Build the cluster with persistence enabled and preload data to it.
> ** Stop one node without baseline change.
> ** Make new data updates.
> ** Return leaved node to the cluster.
> The both tests should be able to run on large amounts of data enough to
> ensure rebalancing time about of several minutes.
> Test parameters:
> # Initial node count (derived from test context);
> # Cache count - the count of caches to create and data preload;
> # Cache entry count - the count of entries per cache to preload;
> # Cache entry size - the size of each cache entry in bytes;
> # Rebalance thread pool size - the value for
> {{IgniteConfiguration#rebalanceThreadPoolSize}} property (see [configuring
> rebalance thread pool
> title|https://ignite.apache.org/docs/latest/data-rebalancing#configuring-rebalance-thread-pool]),
> expected that greater value makes rebalance faster.
> # Rebalance batch size - the value for
> {{IgniteConfiguration#rebalanceBatchSize}} property (see [other rebalance
> properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
> expected that greater value makes rebalance faster on large data or
> [throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling]
> enabled (rebalanceThrottling > 0).
> # Rebalance throttle - the value for
> {{IgniteConfiguration#rebalanceThrottle}} property (see [rebalance message
> throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling],
> [other rebalance
> properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
> 0 - throttling disabled, greater value makes rebalance slower.
> Test result: rebalance statistics.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-14477) Ducktape test of rebalance for persistent mode
[
https://issues.apache.org/jira/browse/IGNITE-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergei Ryzhov updated IGNITE-14477:
---
Description:
This test should check the rebalance on persistent caches in two scenarios:
# Full rebalance which triggered by two event types: node join and node left
the topology (need to update baseline topology).
# Historical rebalance which triggered by joining to cluster of missed node
with existing PDS:
** Build the cluster with persistence enabled and preload data to it.
** Stop one node without baseline change.
** Make new data updates.
** Return leaved node to the cluster.
The both tests should be able to run on large amounts of data enough to ensure
rebalancing time about of several minutes.
Test parameters:
# Initial node count (derived from test context);
# Cache count - the count of caches to create and data preload;
# Cache entry count - the count of entries per cache to preload;
# Cache entry size - the size of each cache entry in bytes;
# Rebalance thread pool size - the value for
{{IgniteConfiguration#rebalanceThreadPoolSize}} property (see [configuring
rebalance thread pool
title|https://ignite.apache.org/docs/latest/data-rebalancing#configuring-rebalance-thread-pool]),
expected that greater value makes rebalance faster.
# Rebalance batch size - the value for
{{IgniteConfiguration#rebalanceBatchSize}} property (see [other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
expected that greater value makes rebalance faster on large data or
[throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling]
enabled (rebalanceThrottling > 0).
# Rebalance throttle - the value for {{IgniteConfiguration#rebalanceThrottle}}
property (see [rebalance message
throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling],
[other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
0 - throttling disabled, greater value makes rebalance slower.
Test result: rebalance statistics.
was:
This test should check the rebalance on persistent caches in two scenarios:
# Full rebalance which triggered by two event types: node join and node left
the topology (need to enable baseline auto-adjust and setting the small
baseline auto-adjust timeout).
# Historical rebalance which triggered by joining to cluster of missed node
with existing PDS:
** Build the cluster with persistence enabled and preload data to it.
** Stop one node without baseline change.
** Make new data updates.
** Return leaved node to the cluster.
The both tests should be able to run on large amounts of data enough to ensure
rebalancing time about of several minutes.
Test parameters:
# Initial node count (derived from test context);
# Cache count - the count of caches to create and data preload;
# Cache entry count - the count of entries per cache to preload;
# Cache entry size - the size of each cache entry in bytes;
# Rebalance thread pool size - the value for
{{IgniteConfiguration#rebalanceThreadPoolSize}} property (see [configuring
rebalance thread pool
title|https://ignite.apache.org/docs/latest/data-rebalancing#configuring-rebalance-thread-pool]),
expected that greater value makes rebalance faster.
# Rebalance batch size - the value for
{{IgniteConfiguration#rebalanceBatchSize}} property (see [other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
expected that greater value makes rebalance faster on large data or
[throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling]
enabled (rebalanceThrottling > 0).
# Rebalance throttle - the value for {{IgniteConfiguration#rebalanceThrottle}}
property (see [rebalance message
throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling],
[other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
0 - throttling disabled, greater value makes rebalance slower.
Test result: rebalance statistics.
> Ducktape test of rebalance for persistent mode
> --
>
> Key: IGNITE-14477
> URL: https://issues.apache.org/jira/browse/IGNITE-14477
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Sorokin
>Assignee: Sergei Ryzhov
>Priority: Major
> Labels: IEP-56
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> This test should check the rebalance on persistent caches in two scenarios:
> # Full rebalance which triggered by two event types: node join and node left
> the topology (need to update baseline topology).
> # Historical rebalance which triggered by joining to cluster of missed node
> with existing PDS:
> ** Build the cluster with persistenc
[jira] [Updated] (IGNITE-14477) Ducktape test of rebalance for persistent mode
[
https://issues.apache.org/jira/browse/IGNITE-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Sorokin updated IGNITE-14477:
-
Description:
This test should check the rebalance on persistent caches in two scenarios:
# Full rebalance which triggered by two event types: node join and node left
the topology (need to enable baseline auto-adjust and setting the small
baseline auto-adjust timeout).
# Historical rebalance which triggered by joining to cluster of missed node
with existing PDS:
** Build the cluster with persistence enabled and preload data to it.
** Stop one node without baseline change.
** Make new data updates.
** Return leaved node to the cluster.
The both tests should be able to run on large amounts of data enough to ensure
rebalancing time about of several minutes.
Test parameters:
# Initial node count (derived from test context);
# Cache count - the count of caches to create and data preload;
# Cache entry count - the count of entries per cache to preload;
# Cache entry size - the size of each cache entry in bytes;
# Rebalance thread pool size - the value for
{{IgniteConfiguration#rebalanceThreadPoolSize}} property (see [configuring
rebalance thread pool
title|https://ignite.apache.org/docs/latest/data-rebalancing#configuring-rebalance-thread-pool]),
expected that greater value makes rebalance faster.
# Rebalance batch size - the value for
{{IgniteConfiguration#rebalanceBatchSize}} property (see [other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
expected that greater value makes rebalance faster on large data or
[throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling]
enabled (rebalanceThrottling > 0).
# Rebalance throttle - the value for {{IgniteConfiguration#rebalanceThrottle}}
property (see [rebalance message
throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling],
[other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
0 - throttling disabled, greater value makes rebalance slower.
Test result: rebalance statistics.
was:
This test should check the rebalance on persistent caches in basic scenario:
rebalance triggered by two event types: node join and node left the topology
(need to enable baseline auto-adjust and setting the small baseline auto-adjust
timeout).
The test should be able to run on large amounts of data enough to ensure
rebalancing time about of several minutes.
Test parameters:
# Initial node count (derived from test context);
# Cache count - the count of caches to create and data preload;
# Cache entry count - the count of entries per cache to preload;
# Cache entry size - the size of each cache entry in bytes;
# Rebalance thread pool size - the value for
{{IgniteConfiguration#rebalanceThreadPoolSize}} property (see [configuring
rebalance thread pool
title|https://ignite.apache.org/docs/latest/data-rebalancing#configuring-rebalance-thread-pool]),
expected that greater value makes rebalance faster.
# Rebalance batch size - the value for
{{IgniteConfiguration#rebalanceBatchSize}} property (see [other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
expected that greater value makes rebalance faster on large data or
[throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling]
enabled (rebalanceThrottling > 0).
# Rebalance throttle - the value for {{IgniteConfiguration#rebalanceThrottle}}
property (see [rebalance message
throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling],
[other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
0 - throttling disabled, greater value makes rebalance slower.
# WAL rebalance - using WAL (historical) rebalance instead of full rebalance.
Test result: rebalance statistics.
> Ducktape test of rebalance for persistent mode
> --
>
> Key: IGNITE-14477
> URL: https://issues.apache.org/jira/browse/IGNITE-14477
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Sorokin
>Assignee: Dmitriy Sorokin
>Priority: Major
> Labels: IEP-56
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This test should check the rebalance on persistent caches in two scenarios:
> # Full rebalance which triggered by two event types: node join and node left
> the topology (need to enable baseline auto-adjust and setting the small
> baseline auto-adjust timeout).
> # Historical rebalance which triggered by joining to cluster of missed node
> with existing PDS:
> ** Build the cluster with persistence enabled and preload data to it.
> ** Stop one node without baseline change.
> ** Make new data up
[jira] [Updated] (IGNITE-14477) Ducktape test of rebalance for persistent mode
[
https://issues.apache.org/jira/browse/IGNITE-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Sorokin updated IGNITE-14477:
-
Description:
This test should check the rebalance on persistent caches in basic scenario:
rebalance triggered by two event types: node join and node left the topology
(need to enable baseline auto-adjust and setting the small baseline auto-adjust
timeout).
The test should be able to run on large amounts of data enough to ensure
rebalancing time about of several minutes.
Test parameters:
# Initial node count (derived from test context);
# Cache count - the count of caches to create and data preload;
# Cache entry count - the count of entries per cache to preload;
# Cache entry size - the size of each cache entry in bytes;
# Rebalance thread pool size - the value for
{{IgniteConfiguration#rebalanceThreadPoolSize}} property (see [configuring
rebalance thread pool
title|https://ignite.apache.org/docs/latest/data-rebalancing#configuring-rebalance-thread-pool]),
expected that greater value makes rebalance faster.
# Rebalance batch size - the value for
{{IgniteConfiguration#rebalanceBatchSize}} property (see [other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
expected that greater value makes rebalance faster on large data or
[throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling]
enabled (rebalanceThrottling > 0).
# Rebalance throttle - the value for {{IgniteConfiguration#rebalanceThrottle}}
property (see [rebalance message
throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling],
[other rebalance
properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
0 - throttling disabled, greater value makes rebalance slower.
# WAL rebalance - using WAL (historical) rebalance instead of full rebalance.
Test result: rebalance statistics.
> Ducktape test of rebalance for persistent mode
> --
>
> Key: IGNITE-14477
> URL: https://issues.apache.org/jira/browse/IGNITE-14477
> Project: Ignite
> Issue Type: Sub-task
>Reporter: Dmitriy Sorokin
>Assignee: Dmitriy Sorokin
>Priority: Major
> Labels: IEP-56
>
> This test should check the rebalance on persistent caches in basic scenario:
> rebalance triggered by two event types: node join and node left the topology
> (need to enable baseline auto-adjust and setting the small baseline
> auto-adjust timeout).
> The test should be able to run on large amounts of data enough to ensure
> rebalancing time about of several minutes.
> Test parameters:
> # Initial node count (derived from test context);
> # Cache count - the count of caches to create and data preload;
> # Cache entry count - the count of entries per cache to preload;
> # Cache entry size - the size of each cache entry in bytes;
> # Rebalance thread pool size - the value for
> {{IgniteConfiguration#rebalanceThreadPoolSize}} property (see [configuring
> rebalance thread pool
> title|https://ignite.apache.org/docs/latest/data-rebalancing#configuring-rebalance-thread-pool]),
> expected that greater value makes rebalance faster.
> # Rebalance batch size - the value for
> {{IgniteConfiguration#rebalanceBatchSize}} property (see [other rebalance
> properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
> expected that greater value makes rebalance faster on large data or
> [throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling]
> enabled (rebalanceThrottling > 0).
> # Rebalance throttle - the value for
> {{IgniteConfiguration#rebalanceThrottle}} property (see [rebalance message
> throttling|https://ignite.apache.org/docs/latest/data-rebalancing#throttling],
> [other rebalance
> properties|https://ignite.apache.org/docs/latest/data-rebalancing#other-properties]),
> 0 - throttling disabled, greater value makes rebalance slower.
> # WAL rebalance - using WAL (historical) rebalance instead of full rebalance.
> Test result: rebalance statistics.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
