[
https://issues.apache.org/jira/browse/IGNITE-12549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046862#comment-17046862
]
Ignite TC Bot commented on IGNITE-12549:
----------------------------------------
{panel:title=Branch: [pull/7277/head] Base: [master] : Possible Blockers
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 5{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5086421]]
* IgniteCacheWithIndexingTestSuite:
ClusterReadOnlyModeDoesNotBreakSqlSelectTest.test - Test has low fail rate in
base branch 0,0% and is not flaky
{color:#d04437}Scala (Examples){color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5086389]]
{color:#d04437}Basic 1{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5086396]]
* IgniteBasicTestSuite: BPlusTreeFakeReuseSelfTest.testMassiveRemove2_true -
Test has low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Basic 2{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=5086356]]
* IgniteComputeBasicConfigVariationsFullApiTestSuite:
IgniteComputeConfigVariationsFullApiTest_46.testDeployExecuteByName - Test has
low fail rate in base branch 0,0% and is not flaky
{color:#d04437}Thin client: Python{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=5086445]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5086468&buildTypeId=IgniteTests24Java8_RunAll]
> Scan query/iterator on a replicated cache may get wrong results
> ---------------------------------------------------------------
>
> Key: IGNITE-12549
> URL: https://issues.apache.org/jira/browse/IGNITE-12549
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.7.6
> Reporter: Sergey Kosarev
> Assignee: Sergey Kosarev
> Priority: Critical
> Fix For: 2.9, 2.8.1
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> Case 1
> 1. start server node 1
> 2. create and fill replicated cache with RebalanceMode.Async (as by default)
> 3. start servr node 2
> 4. immediately execute scan query on the replicated cache((or just iterate
> the cache)) on the node 2
> It can get empty or partial results. (if rebalance on node 2 is finished)
> Case 2
> 1. start server node 1
> 2. create and fill replicated cache with RebalanceMode.Async (as by default)
> 3. start client node 2
> 4. start server node 3
> 5. immediately execute scan query on the replicated cache((or just iterate
> the cache)) on the client node 2
> It can get empty or partial results. (if rebalance on node 2 is not finished
> and query is mapped on the node 2)
> It looks like problem in the
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter#nodes()
> case REPLICATED:
> if (prj != null || part != null)
> return nodes(cctx, prj, part);
> if (cctx.affinityNode())
> return *Collections.singletonList(cctx.localNode())*;
> Collection<ClusterNode> affNodes = nodes(cctx, null, null);
> return affNodes.isEmpty() ? affNodes :
> *Collections.singletonList(F.rand(affNodes))*;
> case PARTITIONED:
> return nodes(cctx, prj, part);
> which is executed in
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryAdapter#executeScanQuery.
> If executed on a just started node it obviously returns the local node
> disregarding was it rebalanced or not.
> If executed on a client it returns a random affinity node, so it also can be
> not yet rebalanced node.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
