[
https://issues.apache.org/jira/browse/IGNITE-27696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maksim Timonin updated IGNITE-27696:
------------------------------------
Description:
When IndexQuery.setPartition is set, IndexQuery can query local backup
partition instead of remote primary partition, even for partitioned caches.
This breaks ReadOwnWrites consistency.
The bug happens due to 2 issues:
# CacheQuery#nodes mixes nodes that own partition (primary is not first)
# CacheQueryDistributedFuture#nodes always returns local node if it owns
partition (even if it backup).
was:
IndexQuery might query local backup partition instead of remote primary
partition. It happens when setPartition is used.
This breaks ReadOwnWrites consistency
> IndexQuery queries backups instead of primary partitions
> --------------------------------------------------------
>
> Key: IGNITE-27696
> URL: https://issues.apache.org/jira/browse/IGNITE-27696
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: 2.18-review
> Time Spent: 50m
> Remaining Estimate: 0h
>
> When IndexQuery.setPartition is set, IndexQuery can query local backup
> partition instead of remote primary partition, even for partitioned caches.
> This breaks ReadOwnWrites consistency.
> The bug happens due to 2 issues:
> # CacheQuery#nodes mixes nodes that own partition (primary is not first)
> # CacheQueryDistributedFuture#nodes always returns local node if it owns
> partition (even if it backup).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
