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

Iurii Gerzhedovich updated IGNITE-22466:
----------------------------------------
    Description: 
At the moment, mapping service support mapping only on primary replicas. To 
improve data colocation, we may use backup replicas as well for RO queries.

Let's improve mapping service in order to take advantage of backups locality 
and minimize amount data sent over the network.

Some failures that should be considered during implementation:
 * Replica is not ready yet
 * Replica has already gone
 * Replica may be too outdated (safeTime of the replica is far behind of 
safeTime of the primary)
 * Anything else?

  was:
At the moment, mapping service support mapping only on primary replicas. To 
improve data colocation, we may use backup replicas as well for RO queries.

Let's improve mapping service in order to take advantage of backups locality 
and minimize amount data sent over the network.

Some failures that should be considered during implementation:
* Replica is not ready yet
* Replica has already gone
* Replica may be too outdated (safeTime of the replica is far behind of 
safeTime of the primary)
* Anything else?   


> Sql. Support mapping on backup replicas
> ---------------------------------------
>
>                 Key: IGNITE-22466
>                 URL: https://issues.apache.org/jira/browse/IGNITE-22466
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> At the moment, mapping service support mapping only on primary replicas. To 
> improve data colocation, we may use backup replicas as well for RO queries.
> Let's improve mapping service in order to take advantage of backups locality 
> and minimize amount data sent over the network.
> Some failures that should be considered during implementation:
>  * Replica is not ready yet
>  * Replica has already gone
>  * Replica may be too outdated (safeTime of the replica is far behind of 
> safeTime of the primary)
>  * Anything else?



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

Reply via email to