[jira] [Resolved] (IGNITE-15835) Add control.sh utility feature to detect partition reserve counter(HWM) inconsistency.
[ https://issues.apache.org/jira/browse/IGNITE-15835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov resolved IGNITE-15835. -- Resolution: Duplicate > Add control.sh utility feature to detect partition reserve counter(HWM) > inconsistency. > -- > > Key: IGNITE-15835 > URL: https://issues.apache.org/jira/browse/IGNITE-15835 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Major > Labels: ise > > Check during idle_verify that update and reserve counters are consistent (HWM > >= LWM). > The current transaction protocol implementation allows lagging of HWM from > LWM on *backup* partitions. Therefore, idle_verify should check only primary > partitions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-16362) Local state recovery
[ https://issues.apache.org/jira/browse/IGNITE-16362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-16362: - Description: *Local state recovery* is changing local state in a way that every component on the node has its state configured and updated accordingly to cluster-wide configuration, topology, stored data, etc. and all the events that change this state and had already happened in the cluster to the moment in which the node tried to join the cluster. was:*Local state recovery* is changing local state in a way that every component on the node has its state configured and updated accordingly to cluster-wide configuration, topology, stored data, etc. and all the events that change this state and had already happened in the cluster to the moment in which the node tried to join the cluster. > Local state recovery > > > Key: IGNITE-16362 > URL: https://issues.apache.org/jira/browse/IGNITE-16362 > Project: Ignite > Issue Type: Epic >Reporter: Denis Chudov >Priority: Major > Labels: ignite-3 > > *Local state recovery* is changing local state in a way that every component > on the node has its state configured and updated accordingly to cluster-wide > configuration, topology, stored data, etc. and all the events that change > this state and had already happened in the cluster to the moment in which the > node tried to join the cluster. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Labels: syncbottest (was: )
> Add separate configuration for system data region
> -
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Labels: syncbottest
> Fix For: 2.13
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Comment Edited] (IGNITE-15998) Add separate configuration for system data region
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452527#comment-17452527
]
Eduard Rakhmankulov edited comment on IGNITE-15998 at 12/30/21, 2:04 PM:
-
[~Smolnikov] Please take a look.
was (Author: erixon):
[~Smolnikov] please take a look.
> Add separate configuration for system data region
> -
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Labels: (was: test)
> Add separate configuration for system data region
> -
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Labels: test (was: )
> Add separate configuration for system data region
> -
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Labels: test
> Fix For: 2.13
>
> Time Spent: 3h
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17455238#comment-17455238
]
Eduard Rakhmankulov commented on IGNITE-15998:
--
[~ptupitsyn] good day, I've fixed the issues you've mentioned and rerun the
tests. Please look at the patch again.
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17453890#comment-17453890
]
Eduard Rakhmankulov commented on IGNITE-15998:
--
[~ptupitsyn] can you review changes in .net API?
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17453023#comment-17453023
]
Eduard Rakhmankulov commented on IGNITE-15998:
--
[~Smolnikov] Thank you for your comments. I've fixed issues and answered
comments.
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Commented] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17452527#comment-17452527
]
Eduard Rakhmankulov commented on IGNITE-15998:
--
[~Smolnikov] please take a look.
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-16047) Add documentation for new way to configure system data region.
Eduard Rakhmankulov created IGNITE-16047: Summary: Add documentation for new way to configure system data region. Key: IGNITE-16047 URL: https://issues.apache.org/jira/browse/IGNITE-16047 Project: Ignite Issue Type: Improvement Components: documentation Affects Versions: 2.13 Reporter: Eduard Rakhmankulov -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Release Note: Move system data region configuration to its own class.
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Fix Version/s: 2.13
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Component/s: cache
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
> Components: cache
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Fix For: 2.13
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Description:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good either.
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
was:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good either.
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
dev-list discussion:
https://lists.apache.org/thread/gqtflo75wrmj14z6496bh0phzfc2lncp
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
>
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Description:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good either.
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
dev-list discussion:
https://lists.apache.org/thread/gqtflo75wrmj14z6496bh0phzfc2lncp
was:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good either.
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
>
[jira] [Updated] (IGNITE-15998) Add separate configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Summary: Add separate configuration for system data region. (was: Add
configuration for system data region.)
> Add separate configuration for system data region.
> --
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (IGNITE-15998) Add configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Description:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good either.
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
was:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good
either.{*}{*}
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
> Add configuration for system data region.
> -
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
>
[jira] [Updated] (IGNITE-15998) Add configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Description:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good
either.{*}{*}
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
was:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good
either.{*}{{*}}
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
> Add configuration for system data region.
> -
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.{*}{*}
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
>
[jira] [Updated] (IGNITE-15998) Add configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Description:
*AS IS*
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good
either.{*}{{*}}
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
was:
AS IS
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good
either.{*}{*}
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
> Add configuration for system data region.
> -
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
>
> *AS IS*
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.{*}{{*}}
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
>
[jira] [Updated] (IGNITE-15998) Add configuration for system data region.
[
https://issues.apache.org/jira/browse/IGNITE-15998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15998:
-
Description:
AS IS
Currently, Ignite users can control only two *system region* parameters:
*initialSize* and *maxSize.* These properties are managed by
DataStorageConfiguration, but same time default and user-specified regions have
*org.apache.ignite.configuration.DataRegionConfiguration* for configuring them.
It is not wise to use the same class for the {*}system region{*}, because there
are some restrictions the codebase is relying on, but keeping to `drill new
holes` in *DataStorageConfiguration* for the *system region* is not good
either.{*}{*}
*TO BE*
Implement configuration class for systemDataRegion similar to
{*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
restricted options, ready to be added more on-demand.
Move systemRegionProperties from
*org.apache.ignite.configuration.DataStorageConfiguration* to own class.
API changes:
# Declare deprecated:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
# Add new methods:
**
org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
**
org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
# Add new configuration class
org.apache.ignite.configuration.SystemDataRegionConfiguration
> Add configuration for system data region.
> -
>
> Key: IGNITE-15998
> URL: https://issues.apache.org/jira/browse/IGNITE-15998
> Project: Ignite
> Issue Type: Improvement
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Major
>
> AS IS
> Currently, Ignite users can control only two *system region* parameters:
> *initialSize* and *maxSize.* These properties are managed by
> DataStorageConfiguration, but same time default and user-specified regions
> have *org.apache.ignite.configuration.DataRegionConfiguration* for
> configuring them. It is not wise to use the same class for the {*}system
> region{*}, because there are some restrictions the codebase is relying on,
> but keeping to `drill new holes` in *DataStorageConfiguration* for the
> *system region* is not good either.{*}{*}
>
> *TO BE*
> Implement configuration class for systemDataRegion similar to
> {*}org.apache.ignite.configuration.DataRegionConfiguration{*}, but with more
> restricted options, ready to be added more on-demand.
> Move systemRegionProperties from
> *org.apache.ignite.configuration.DataStorageConfiguration* to own class.
>
> API changes:
> # Declare deprecated:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionInitialSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemRegionMaxSize
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemRegionMaxSize
> # Add new methods:
> **
> org.apache.ignite.configuration.DataStorageConfiguration#setSystemDataRegionConfiguration(SystemDataRegionConfiguration)
> **
> org.apache.ignite.configuration.DataStorageConfiguration#getSystemDataRegionConfiguration
> # Add new configuration class
> org.apache.ignite.configuration.SystemDataRegionConfiguration
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Created] (IGNITE-15998) Add configuration for system data region.
Eduard Rakhmankulov created IGNITE-15998: Summary: Add configuration for system data region. Key: IGNITE-15998 URL: https://issues.apache.org/jira/browse/IGNITE-15998 Project: Ignite Issue Type: Improvement Reporter: Eduard Rakhmankulov Assignee: Eduard Rakhmankulov -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (IGNITE-15835) Add control.sh utility feature to detect partition reserve counter(HWM) inconsistency.
Eduard Rakhmankulov created IGNITE-15835: Summary: Add control.sh utility feature to detect partition reserve counter(HWM) inconsistency. Key: IGNITE-15835 URL: https://issues.apache.org/jira/browse/IGNITE-15835 Project: Ignite Issue Type: Improvement Reporter: Eduard Rakhmankulov Assignee: Eduard Rakhmankulov Check during idle_verify that update and reserve counters are consistent (HWM >= LWM). The current transaction protocol implementation allows lagging of HWM from LWM on *backup* partitions. Therefore, idle_verify should check only primary partitions. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-15716) Fix StackOverflowError in case if exception suppressed with itself
[
https://issues.apache.org/jira/browse/IGNITE-15716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427659#comment-17427659
]
Eduard Rakhmankulov commented on IGNITE-15716:
--
Those suites timeout on master too, possibly
https://issues.apache.org/jira/browse/IGNITE-15678 is the reason.
> Fix StackOverflowError in case if exception suppressed with itself
> --
>
> Key: IGNITE-15716
> URL: https://issues.apache.org/jira/browse/IGNITE-15716
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.11
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We can get infinite loop in
> org.apache.ignite.internal.util.typedef.X#hasCause and X#cause in case if
> exception is suppressed with itself.
> Example:
> {code:java}
> Exception e = new Exception("foo");
> Exception e2 = new Exception(e);
> e.addSuppressed(e2)
> {code}
>
> Stack:
> {code:java}
> java.lang.StackOverflowError: null
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:476)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-15716) Fix StackOverflowError in case if exception suppressed with itself
[
https://issues.apache.org/jira/browse/IGNITE-15716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17427181#comment-17427181
]
Eduard Rakhmankulov commented on IGNITE-15716:
--
sorry forgot about visa.
> Fix StackOverflowError in case if exception suppressed with itself
> --
>
> Key: IGNITE-15716
> URL: https://issues.apache.org/jira/browse/IGNITE-15716
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.11
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We can get infinite loop in
> org.apache.ignite.internal.util.typedef.X#hasCause and X#cause in case if
> exception is suppressed with itself.
> Example:
> {code:java}
> Exception e = new Exception("foo");
> Exception e2 = new Exception(e);
> e.addSuppressed(e2)
> {code}
>
> Stack:
> {code:java}
> java.lang.StackOverflowError: null
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:476)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15716) Fix StackOverflowError in case if exception suppressed with itself
[
https://issues.apache.org/jira/browse/IGNITE-15716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15716:
-
Affects Version/s: 2.11
> Fix StackOverflowError in case if exception suppressed with itself
> --
>
> Key: IGNITE-15716
> URL: https://issues.apache.org/jira/browse/IGNITE-15716
> Project: Ignite
> Issue Type: Bug
>Affects Versions: 2.11
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Minor
>
> We can get infinite loop in
> org.apache.ignite.internal.util.typedef.X#hasCause and X#cause in case if
> exception is suppressed with itself.
> Example:
> {code:java}
> Exception e = new Exception("foo");
> Exception e2 = new Exception(e);
> e.addSuppressed(e2)
> {code}
>
> Stack:
> {code:java}
> java.lang.StackOverflowError: null
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:476)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-15716) Fix StackOverflowError in case if exception suppressed with itself
[
https://issues.apache.org/jira/browse/IGNITE-15716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eduard Rakhmankulov updated IGNITE-15716:
-
Description:
We can get infinite loop in org.apache.ignite.internal.util.typedef.X#hasCause
and X#cause in case if exception is suppressed with itself.
Example:
{code:java}
Exception e = new Exception("foo");
Exception e2 = new Exception(e);
e.addSuppressed(e2)
{code}
Stack:
{code:java}
java.lang.StackOverflowError: null
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:476)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
{code}
was:
We can get infinite loop in org.apache.ignite.internal.util.typedef.X#hasCause
in case if exception is suppressed with itself.
Example
{{Exception e = new Exception("foo");
Exception e2 = new Exception(e);
e.addSuppressed(e2)}}
Stack:
{{java.lang.StackOverflowError: null
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:476)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
}}
Also it’s going to be prefect to investigate if there any places where we can
suppress the same exception.
> Fix StackOverflowError in case if exception suppressed with itself
> --
>
> Key: IGNITE-15716
> URL: https://issues.apache.org/jira/browse/IGNITE-15716
> Project: Ignite
> Issue Type: Bug
>Reporter: Eduard Rakhmankulov
>Assignee: Eduard Rakhmankulov
>Priority: Minor
>
> We can get infinite loop in
> org.apache.ignite.internal.util.typedef.X#hasCause and X#cause in case if
> exception is suppressed with itself.
> Example:
> {code:java}
> Exception e = new Exception("foo");
> Exception e2 = new Exception(e);
> e.addSuppressed(e2)
> {code}
>
> Stack:
> {code:java}
> java.lang.StackOverflowError: null
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:476)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
> at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
>
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-15716) Fix StackOverflowError in case if exception suppressed with itself
Eduard Rakhmankulov created IGNITE-15716:
Summary: Fix StackOverflowError in case if exception suppressed
with itself
Key: IGNITE-15716
URL: https://issues.apache.org/jira/browse/IGNITE-15716
Project: Ignite
Issue Type: Bug
Reporter: Eduard Rakhmankulov
Assignee: Eduard Rakhmankulov
We can get infinite loop in org.apache.ignite.internal.util.typedef.X#hasCause
in case if exception is suppressed with itself.
Example
{{Exception e = new Exception("foo");
Exception e2 = new Exception(e);
e.addSuppressed(e2)}}
Stack:
{{java.lang.StackOverflowError: null
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:476)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
at org.apache.ignite.internal.util.typedef.X.hasCause(X.java:489)
}}
Also it’s going to be prefect to investigate if there any places where we can
suppress the same exception.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382057#comment-17382057 ] Eduard Rakhmankulov commented on IGNITE-14728: -- Small remark: the test was rerun for commit before the last. The last commit is fixing of typo in javadoc. > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Minor > Time Spent: 2h 20m > Remaining Estimate: 0h > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most part > of users. > I propose the creation of a new DMS property *history.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *history.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > # On property check print to log value and source of value. > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. > Dev list discussion > [http://apache-ignite-developers.2346864.n4.nabble.com/Change-IGNITE-PDS-WAL-REBALANCE-THRESHOLD-from-System-property-to-Configuraton-tp52560.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17382056#comment-17382056 ] Eduard Rakhmankulov commented on IGNITE-14728: -- [~sk0x50] I've fixed your comments and rerun affecting test suite: https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_ControlUtility/6089193 > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Minor > Time Spent: 2h 20m > Remaining Estimate: 0h > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most part > of users. > I propose the creation of a new DMS property *history.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *history.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > # On property check print to log value and source of value. > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. > Dev list discussion > [http://apache-ignite-developers.2346864.n4.nabble.com/Change-IGNITE-PDS-WAL-REBALANCE-THRESHOLD-from-System-property-to-Configuraton-tp52560.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-15135) Collect all public distrubuted properties in one place.
Eduard Rakhmankulov created IGNITE-15135:
Summary: Collect all public distrubuted properties in one place.
Key: IGNITE-15135
URL: https://issues.apache.org/jira/browse/IGNITE-15135
Project: Ignite
Issue Type: Improvement
Reporter: Eduard Rakhmankulov
In Ignite we have various distributed properties stored in metastorage. Some
of that is the public - a user can change it through control.sh utility.
Now we have a bunch of properties that are registered with "hardcoded" names in
code e.g.:
{code:java}
kernalCtx.internalSubscriptionProcessor().registerDatabaseListener(new
MetastorageRecoveryLifecycle()); cpFreqDeviation = new
SimpleDistributedProperty<>("checkpoint.deviation", Integer::parseInt);
kernalCtx.internalSubscriptionProcessor().registerDistributedConfigurationListener(dispatcher
-> { cpFreqDeviation.addListener((name, oldVal, newVal) -> U.log(log,
"Checkpoint frequency deviation changed [oldVal=" + oldVal + ", newVal=" +
newVal + "]")); dispatcher.registerProperty(cpFreqDeviation); });
{code}
I propose to gather all names of public distributed properties similar to
org.apache.ignite.IgniteSystemProperties.
A list of current distributed properties should be included (need to analyze;
probably there are more of this):
* checkpoint.deviation
* historical.rebalance.threshold
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17379834#comment-17379834 ] Eduard Rakhmankulov commented on IGNITE-14728: -- [~alapin] please take a look. > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Minor > Time Spent: 1h 20m > Remaining Estimate: 0h > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most part > of users. > I propose the creation of a new DMS property *history.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *history.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > # On property check print to log value and source of value. > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. > Dev list discussion > [http://apache-ignite-developers.2346864.n4.nabble.com/Change-IGNITE-PDS-WAL-REBALANCE-THRESHOLD-from-System-property-to-Configuraton-tp52560.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14728: - Description: We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that determines a count of entries of partition starting from which cluster will try applying historical rebalance for that partition. But the system property is not convenient to use and is hidden from most part of users. I propose the creation of a new DMS property *history.rebalance.threshold* instead of a system property. The next algorithm will be used: # On node start *history.rebalance.threshold* property will be checked. # If there is no value, then the old system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. # If a system property is not defined then the default value from java will be written to DMS (*500*). # On property check print to log value and source of value. Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. Dev list discussion [http://apache-ignite-developers.2346864.n4.nabble.com/Change-IGNITE-PDS-WAL-REBALANCE-THRESHOLD-from-System-property-to-Configuraton-tp52560.html] was: We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that determines a count of entries of partition starting from which cluster will try applying historical rebalance for that partition. But the system property is not convenient to use and is hidden from most part of users. I propose the creation of a new DMS property *wal.rebalance.threshold* instead of a system property. The next algorithm will be used: # On node start *wal.rebalance.threshold* property will be checked. # If there is no value, then the old system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. # If a system property is not defined then the default value from java will be written to DMS (*500*). # On property check print to log value and source of value. Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. Dev list discussion http://apache-ignite-developers.2346864.n4.nabble.com/Change-IGNITE-PDS-WAL-REBALANCE-THRESHOLD-from-System-property-to-Configuraton-tp52560.html > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most part > of users. > I propose the creation of a new DMS property *history.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *history.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > # On property check print to log value and source of value. > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. > Dev list discussion > [http://apache-ignite-developers.2346864.n4.nabble.com/Change-IGNITE-PDS-WAL-REBALANCE-THRESHOLD-from-System-property-to-Configuraton-tp52560.html] > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17350335#comment-17350335 ] Eduard Rakhmankulov commented on IGNITE-14728: -- [~alapin] please take a look. > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most > part of users. > I propose the creation of a new DMS property *wal.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *wal.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > # On property check print to log value and source of value. > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17349282#comment-17349282 ] Eduard Rakhmankulov commented on IGNITE-14728: -- [~Denis Chudov] please look again > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most > part of users. > I propose the creation of a new DMS property *wal.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *wal.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > # On property check print to log value and source of value. > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14728: - Description: We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that determines a count of entries of partition starting from which cluster will try applying historical rebalance for that partition. But the system property is not convenient to use and is hidden from most part of users. I propose the creation of a new DMS property *wal.rebalance.threshold* instead of a system property. The next algorithm will be used: # On node start *wal.rebalance.threshold* property will be checked. # If there is no value, then the old system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. # If a system property is not defined then the default value from java will be written to DMS (*500*). # On property check print to log value and source of value. Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. was: We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that determines a count of entries of partition starting from which cluster will try applying historical rebalance for that partition. But the system property is not convenient to use and is hidden from most part of users. I propose the creation of a new DMS property *wal.rebalance.threshold* instead of a system property. The next algorithm will be used: # On node start *wal.rebalance.threshold* property will be checked. # If there is no value, then the old system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. # If a system property is not defined then the default value from java will be written to DMS (*500*). Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Priority: Minor > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most > part of users. > I propose the creation of a new DMS property *wal.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *wal.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > # On property check print to log value and source of value. > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov reassigned IGNITE-14728: Assignee: Eduard Rakhmankulov > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Assignee: Eduard Rakhmankulov >Priority: Minor > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most > part of users. > I propose the creation of a new DMS property *wal.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *wal.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > # On property check print to log value and source of value. > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14728: - Description: We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that determines a count of entries of partition starting from which cluster will try applying historical rebalance for that partition. But the system property is not convenient to use and is hidden from most part of users. I propose the creation of a new DMS property *wal.rebalance.threshold* instead of a system property. The next algorithm will be used: # On node start *wal.rebalance.threshold* property will be checked. # If there is no value, then the old system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. # If a system property is not defined then the default value from java will be written to DMS (*500*). Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. was: We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that determines a count of entries of partition starting from which cluster will try applying historical rebalance for that partition. But the system property is not convenient to use and is hidden from most part of users. I propose the creation of a new DMS property *wal.rebalance.threshold* instead of a system property. Next algorithm will be used: # On node start *wal.rebalance.threshold* property will be checked. If there are no value, then old system property > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Priority: Minor > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most > part of users. > I propose the creation of a new DMS property *wal.rebalance.threshold* > instead of a system property. > The next algorithm will be used: > # On node start *wal.rebalance.threshold* property will be checked. > # If there is no value, then the old system property > *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* value will be written to DMS. > # If a system property is not defined then the default value from java will > be written to DMS (*500*). > Mark the system property *IGNITE_PDS_WAL_REBALANCE_THRESHOLD* as deprecated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
[ https://issues.apache.org/jira/browse/IGNITE-14728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14728: - Description: We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that determines a count of entries of partition starting from which cluster will try applying historical rebalance for that partition. But the system property is not convenient to use and is hidden from most part of users. I propose the creation of a new DMS property *wal.rebalance.threshold* instead of a system property. Next algorithm will be used: # On node start *wal.rebalance.threshold* property will be checked. If there are no value, then old system property > Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed > property > -- > > Key: IGNITE-14728 > URL: https://issues.apache.org/jira/browse/IGNITE-14728 > Project: Ignite > Issue Type: Improvement >Reporter: Eduard Rakhmankulov >Priority: Minor > > We have a system property named "IGNITE_PDS_WAL_REBALANCE_THRESHOLD", that > determines a count of entries of partition starting from which cluster will > try applying historical rebalance for that partition. > But the system property is not convenient to use and is hidden from most part > of users. > I propose the creation of a new DMS property *wal.rebalance.threshold* > instead of a system property. > Next algorithm will be used: > # On node start *wal.rebalance.threshold* property will be checked. If there > are no value, then old system property -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-14728) Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property
Eduard Rakhmankulov created IGNITE-14728: Summary: Change IGNITE_PDS_WAL_REBALANCE_THRESHOLD from System property to Distributed property Key: IGNITE-14728 URL: https://issues.apache.org/jira/browse/IGNITE-14728 Project: Ignite Issue Type: Improvement Reporter: Eduard Rakhmankulov -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339709#comment-17339709 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~sergeychugunov] please look > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14469: - Reviewer: Sergey Chugunov (was: Sergey Chugunov) > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339706#comment-17339706 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~sergey-chugunov] please look > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14469: - Component/s: (was: sql) > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14469: - Reviewer: Sergey Chugunov > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339691#comment-17339691 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~ktkale...@gridgain.com] Checkstyle suite run https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_CheckCodeStyle/5994954 > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17339544#comment-17339544 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~ktkale...@gridgain.com] look again please > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14469: - Release Note: Utility control.sh outputs list of indices that will not be forced rebuild. > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1.5h > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eduard Rakhmankulov updated IGNITE-14469: - Reviewer: Kirill Tkalenko > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17337388#comment-17337388 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~ktkale...@gridgain.com] please, look again. > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 1h 10m > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-14469) Adding a list of caches that will not be forced to rebuild indexes to the control.sh --cache indexes_force_rebuild
[ https://issues.apache.org/jira/browse/IGNITE-14469?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17326668#comment-17326668 ] Eduard Rakhmankulov commented on IGNITE-14469: -- [~ktkale...@gridgain.com] please make code review. > Adding a list of caches that will not be forced to rebuild indexes to the > control.sh --cache indexes_force_rebuild > -- > > Key: IGNITE-14469 > URL: https://issues.apache.org/jira/browse/IGNITE-14469 > Project: Ignite > Issue Type: Improvement > Components: control.sh, sql >Reporter: Kirill Tkalenko >Assignee: Eduard Rakhmankulov >Priority: Major > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > After the IGNITE-14321 is implemented, it will be necessary to add to the > command *control.sh --cache indexes_force_rebuild* the ability to display to > the user that the forced rebuilding of the indexes is impossible, since they > are already being rebuilt. -- This message was sent by Atlassian Jira (v8.3.4#803005)
