[ 
https://issues.apache.org/jira/browse/IGNITE-24507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roman Puchkovskiy updated IGNITE-24507:
---------------------------------------
    Reviewer: Roman Puchkovskiy

> Use ZoneReplicationId in InternalTableImpl in case of colocationEnabled
> -----------------------------------------------------------------------
>
>                 Key: IGNITE-24507
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24507
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Alexander Lapin
>            Assignee: Alexander Lapin
>            Priority: Major
>              Labels: ignite-3
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> h3. Motivation
> Currently, there's a tableId->zoneId groupIdConverter in ReplicaManager that, 
> however, only allows to route replica requests from within InternalTableImpl 
> to the proper zone's Replicas. PrimaryReplica awaiting logic still uses table 
> based routing, which is fine in case of TestPlacementDriver but won't work in 
> case of common PlacementDriver. Thus, as a prerequisite for Zone's 
> PlacementDriver introduction, is seems reasonable to switch primaryReplica 
> awaiting logic towards fair zoneIds based requests.
> h3. Definition of Done
>  * groupIdConverter is removed
>  * InternalTableImpl uses fair zoneIds as target replicationGroupIds.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to