[jira] [Updated] (IGNITE-21806) One PrimaryReplica for many tables partitions inside the one zone
[ https://issues.apache.org/jira/browse/IGNITE-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov updated IGNITE-21806: Description: *Motivation* When the IGNITE-18991 we will have ZonePartitionId oriented management inside the PlacementDriver, but still have the number of replicas, which equals to the number of tables per partition in the zone. As a iterative step on the road of "zone based collocation (one RAFT group per zone partition" we must implement the another approach: one PrimaryReplica for many tables partitions inside the zone. So, in the case of 2 tables inside the 1 zone we must have 1 PrimaryReplica per partition. *Definition of done* Prepare design and according ticket breakdown for the feature implementation was: *Motivation* When the IGNITE-18991 we will have ZonePartitionId oriented management inside the PlacementDriver, but still have the number of replicas, which equals to the number of tables per partition in the zone. As a iterative step on the road of "zone based collocation (one RAFT group per zone partition" we must implement the another approach: one PrimaryReplica for many tables partitions inside the zone. So, in the case of 2 tables inside the 1 zone we must have 1 PrimaryReplica per partition. *Definition of done* If the zone has N tables with M partitions, it must have M PrimaryReplicas - one PrimaryReplica per zone partition. > One PrimaryReplica for many tables partitions inside the one zone > - > > Key: IGNITE-21806 > URL: https://issues.apache.org/jira/browse/IGNITE-21806 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Gusakov >Assignee: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > *Motivation* > When the IGNITE-18991 we will have ZonePartitionId oriented management inside > the PlacementDriver, but still have the number of replicas, which equals to > the number of tables per partition in the zone. As a iterative step on the > road of "zone based collocation (one RAFT group per zone partition" we must > implement the another approach: one PrimaryReplica for many tables partitions > inside the zone. So, in the case of 2 tables inside the 1 zone we must have 1 > PrimaryReplica per partition. > *Definition of done* > Prepare design and according ticket breakdown for the feature implementation -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21806) One PrimaryReplica for many tables partitions inside the one zone
[ https://issues.apache.org/jira/browse/IGNITE-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov updated IGNITE-21806: Epic Link: IGNITE-19170 > One PrimaryReplica for many tables partitions inside the one zone > - > > Key: IGNITE-21806 > URL: https://issues.apache.org/jira/browse/IGNITE-21806 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > *Motivation* > When the IGNITE-18991 we will have ZonePartitionId oriented management inside > the PlacementDriver, but still have the number of replicas, which equals to > the number of tables per partition in the zone. As a iterative step on the > road of "zone based collocation (one RAFT group per zone partition" we must > implement the another approach: one PrimaryReplica for many tables partitions > inside the zone. So, in the case of 2 tables inside the 1 zone we must have 1 > PrimaryReplica per partition. > *Definition of done* > If the zone has N tables with M partitions, it must have M PrimaryReplicas - > one PrimaryReplica per zone partition. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21806) One PrimaryReplica for many tables partitions inside the one zone
[ https://issues.apache.org/jira/browse/IGNITE-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov updated IGNITE-21806: Labels: ignite-3 (was: ) > One PrimaryReplica for many tables partitions inside the one zone > - > > Key: IGNITE-21806 > URL: https://issues.apache.org/jira/browse/IGNITE-21806 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Gusakov >Priority: Major > Labels: ignite-3 > > *Motivation* > When the IGNITE-18991 we will have ZonePartitionId oriented management inside > the PlacementDriver, but still have the number of replicas, which equals to > the number of tables per partition in the zone. As a iterative step on the > road of "zone based collocation (one RAFT group per zone partition" we must > implement the another approach: one PrimaryReplica for many tables partitions > inside the zone. So, in the case of 2 tables inside the 1 zone we must have 1 > PrimaryReplica per partition. > *Definition of done* > If the zone has N tables with M partitions, it must have M PrimaryReplicas - > one PrimaryReplica per zone partition. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-21806) One PrimaryReplica for many tables partitions inside the one zone
[ https://issues.apache.org/jira/browse/IGNITE-21806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kirill Gusakov updated IGNITE-21806: Description: *Motivation* When the IGNITE-18991 we will have ZonePartitionId oriented management inside the PlacementDriver, but still have the number of replicas, which equals to the number of tables per partition in the zone. As a iterative step on the road of "zone based collocation (one RAFT group per zone partition" we must implement the another approach: one PrimaryReplica for many tables partitions inside the zone. So, in the case of 2 tables inside the 1 zone we must have 1 PrimaryReplica per partition. *Definition of done* If the zone has N tables with M partitions, it must have M PrimaryReplicas - one PrimaryReplica per zone partition. > One PrimaryReplica for many tables partitions inside the one zone > - > > Key: IGNITE-21806 > URL: https://issues.apache.org/jira/browse/IGNITE-21806 > Project: Ignite > Issue Type: Improvement >Reporter: Kirill Gusakov >Priority: Major > > *Motivation* > When the IGNITE-18991 we will have ZonePartitionId oriented management inside > the PlacementDriver, but still have the number of replicas, which equals to > the number of tables per partition in the zone. As a iterative step on the > road of "zone based collocation (one RAFT group per zone partition" we must > implement the another approach: one PrimaryReplica for many tables partitions > inside the zone. So, in the case of 2 tables inside the 1 zone we must have 1 > PrimaryReplica per partition. > *Definition of done* > If the zone has N tables with M partitions, it must have M PrimaryReplicas - > one PrimaryReplica per zone partition. -- This message was sent by Atlassian Jira (v8.20.10#820010)