You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Anton Vinogradov (Jira)" <ji...@apache.org> on 2022/05/05 16:39:00 UTC
[jira] [Updated] (IGNITE-16931) Read Repair should support unstable topology
[ https://issues.apache.org/jira/browse/IGNITE-16931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anton Vinogradov updated IGNITE-16931:
--------------------------------------
Parent: IGNITE-15167
Issue Type: Sub-task (was: Improvement)
> Read Repair should support unstable topology
> --------------------------------------------
>
> Key: IGNITE-16931
> URL: https://issues.apache.org/jira/browse/IGNITE-16931
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Anton Vinogradov
> Assignee: Anton Vinogradov
> Priority: Major
> Labels: iep-31
>
> Currently RR does not support unstable topology (when not all owners are located by affinity) and this can be fixed.
> As a start point, it's a good idea to consider a replacement
> {noformat}
> for (KeyCacheObject key : keys) {
> List<ClusterNode> nodes = ctx.affinity().nodesByKey(key, topVer); // affinity
> primaryNodes.put(key, nodes.get(0));
> ...
> {noformat}
> to
> {noformat}
> for (KeyCacheObject key : keys) {
> List<ClusterNode> nodes = ctx.topology().nodes(key.partition(), topVer); // topology
> primaryNodes.put(key, nodes.get(0));
> ...
> {noformat}
> at {{{}org.apache.ignite.internal.processors.cache.distributed.near.consistency.GridNearReadRepairAbstractFuture#map{}}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)