You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ignite.apache.org by "rpuch (via GitHub)" <gi...@apache.org> on 2025/10/16 10:49:09 UTC
[PR] IGNITE-26737 Deprecate non-colocation mode in 3.1 [ignite-3]
rpuch opened a new pull request, #6797:
URL: https://github.com/apache/ignite-3/pull/6797
https://issues.apache.org/jira/browse/IGNITE-26737
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] IGNITE-26737 Deprecate non-colocation mode in 3.1 [ignite-3]
Posted by "IgGusev (via GitHub)" <gi...@apache.org>.
IgGusev commented on code in PR #6797:
URL: https://github.com/apache/ignite-3/pull/6797#discussion_r2435450898
##########
docs/_docs/administrators-guide/storage/data-partitions.adoc:
##########
@@ -120,4 +120,12 @@ NOTE: Reset is likely to result in <<Partition Rebalance>>, which may take a lon
== Partition Rebalance
-When the link:administrators-guide/storage/distribution-zones#cluster-scaling[cluster size changes], Apache Ignite waits for the timeout specified in the `AUTO SCALE UP` or `AUTO SCALE DOWN` distribution zone properties, and then redistributes partitions according to the partition distribution algorithm and transfers data to make it up-to-date with the replication group. This process is called *data rebalance*.
\ No newline at end of file
+When the link:administrators-guide/storage/distribution-zones#cluster-scaling[cluster size changes], Apache Ignite waits for the timeout specified in the `AUTO SCALE UP` or `AUTO SCALE DOWN` distribution zone properties, and then redistributes partitions according to the partition distribution algorithm and transfers data to make it up-to-date with the replication group. This process is called *data rebalance*.
+
+== Old Replication Mode (Table-based Replication)
+
+Most of this page describes the Zone-based Replication which is added in Ignite 3.1 (this is the default now). Ignite 3.0 used Table-based Replication, so clusters created on 3.0 and upgraded to 3.1 will still use Table-based Replication.
+
+Table-based Replication is deprecated since Ignite 3.1, it is planned to be removed in Ignite 3.2. It is recommended to migrate your clusters to Zone-based Replication. Currently, there is no automatic migration tool, so you will need to create a new cluster with Zone-based Replication and move your data there.
+
+You can figure out which replication mode your cluster is using by checking the startup logs, look for the following line: 'Zone based replication: true' or 'Zone based replication: false'. If it's false, you are using Table-based Replication.
Review Comment:
```suggestion
Current replication mode for your cluster is specified in the startup logs. Look for the following line: 'Zone based replication: true' or 'Zone based replication: false'. If it is false, you are using Table-based Replication.
```
##########
docs/_docs/administrators-guide/storage/data-partitions.adoc:
##########
@@ -120,4 +120,12 @@ NOTE: Reset is likely to result in <<Partition Rebalance>>, which may take a lon
== Partition Rebalance
-When the link:administrators-guide/storage/distribution-zones#cluster-scaling[cluster size changes], Apache Ignite waits for the timeout specified in the `AUTO SCALE UP` or `AUTO SCALE DOWN` distribution zone properties, and then redistributes partitions according to the partition distribution algorithm and transfers data to make it up-to-date with the replication group. This process is called *data rebalance*.
\ No newline at end of file
+When the link:administrators-guide/storage/distribution-zones#cluster-scaling[cluster size changes], Apache Ignite waits for the timeout specified in the `AUTO SCALE UP` or `AUTO SCALE DOWN` distribution zone properties, and then redistributes partitions according to the partition distribution algorithm and transfers data to make it up-to-date with the replication group. This process is called *data rebalance*.
+
+== Old Replication Mode (Table-based Replication)
+
+Most of this page describes the Zone-based Replication which is added in Ignite 3.1 (this is the default now). Ignite 3.0 used Table-based Replication, so clusters created on 3.0 and upgraded to 3.1 will still use Table-based Replication.
+
+Table-based Replication is deprecated since Ignite 3.1, it is planned to be removed in Ignite 3.2. It is recommended to migrate your clusters to Zone-based Replication. Currently, there is no automatic migration tool, so you will need to create a new cluster with Zone-based Replication and move your data there.
Review Comment:
```suggestion
Table-based Replication is deprecated in Ignite 3.1, and is planned to be removed in Ignite 3.2. It is recommended to migrate your clusters to Zone-based Replication. Currently, there is no automatic migration tool, so you will need to create a new cluster with Zone-based Replication and move your data there.
```
##########
docs/_docs/administrators-guide/storage/data-partitions.adoc:
##########
@@ -120,4 +120,12 @@ NOTE: Reset is likely to result in <<Partition Rebalance>>, which may take a lon
== Partition Rebalance
-When the link:administrators-guide/storage/distribution-zones#cluster-scaling[cluster size changes], Apache Ignite waits for the timeout specified in the `AUTO SCALE UP` or `AUTO SCALE DOWN` distribution zone properties, and then redistributes partitions according to the partition distribution algorithm and transfers data to make it up-to-date with the replication group. This process is called *data rebalance*.
\ No newline at end of file
+When the link:administrators-guide/storage/distribution-zones#cluster-scaling[cluster size changes], Apache Ignite waits for the timeout specified in the `AUTO SCALE UP` or `AUTO SCALE DOWN` distribution zone properties, and then redistributes partitions according to the partition distribution algorithm and transfers data to make it up-to-date with the replication group. This process is called *data rebalance*.
+
+== Old Replication Mode (Table-based Replication)
+
+Most of this page describes the Zone-based Replication which is added in Ignite 3.1 (this is the default now). Ignite 3.0 used Table-based Replication, so clusters created on 3.0 and upgraded to 3.1 will still use Table-based Replication.
Review Comment:
```suggestion
Ignite 3.1 introduced Zone-based Replication and uses it by default. Ignite 3.0 used Table-based Replication, so clusters created on 3.0 and upgraded to 3.1 will still use Table-based Replication.
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] IGNITE-26737 Deprecate non-colocation mode in 3.1 [ignite-3]
Posted by "sanpwc (via GitHub)" <gi...@apache.org>.
sanpwc commented on code in PR #6797:
URL: https://github.com/apache/ignite-3/pull/6797#discussion_r2435489032
##########
modules/core/src/main/java/org/apache/ignite/internal/lang/IgniteSystemProperties.java:
##########
@@ -44,7 +44,12 @@ public final class IgniteSystemProperties {
public static final String IGNITE_SKIP_STORAGE_UPDATE_IN_BENCHMARK = "IGNITE_SKIP_STORAGE_UPDATE_IN_BENCHMARK";
// TODO https://issues.apache.org/jira/browse/IGNITE-22522 Remove this feature flag.
- /** Enables zone based replication (aka colocation) feature. */
+ /**
+ * Enables zone based replication (aka colocation) feature.
+ *
+ * @deprecated Non-colocation mode is planned to be removed in version 3.2.
+ */
+ @Deprecated(since = "3.1", forRemoval = true)
Review Comment:
Please add corresponding meta 'since = "3.1", forRemoval = true' to
```
@Deprecated
public static boolean colocationEnabled() {
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] IGNITE-26737 Deprecate non-colocation mode in 3.1 [ignite-3]
Posted by "sanpwc (via GitHub)" <gi...@apache.org>.
sanpwc commented on code in PR #6797:
URL: https://github.com/apache/ignite-3/pull/6797#discussion_r2435489032
##########
modules/core/src/main/java/org/apache/ignite/internal/lang/IgniteSystemProperties.java:
##########
@@ -44,7 +44,12 @@ public final class IgniteSystemProperties {
public static final String IGNITE_SKIP_STORAGE_UPDATE_IN_BENCHMARK = "IGNITE_SKIP_STORAGE_UPDATE_IN_BENCHMARK";
// TODO https://issues.apache.org/jira/browse/IGNITE-22522 Remove this feature flag.
- /** Enables zone based replication (aka colocation) feature. */
+ /**
+ * Enables zone based replication (aka colocation) feature.
+ *
+ * @deprecated Non-colocation mode is planned to be removed in version 3.2.
+ */
+ @Deprecated(since = "3.1", forRemoval = true)
Review Comment:
Please add corresponding meta `since = "3.1", forRemoval = true` to
```
@Deprecated
public static boolean colocationEnabled() {
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] IGNITE-26737 Deprecate non-colocation mode in 3.1 [ignite-3]
Posted by "rpuch (via GitHub)" <gi...@apache.org>.
rpuch merged PR #6797:
URL: https://github.com/apache/ignite-3/pull/6797
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@ignite.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org