[
https://issues.apache.org/jira/browse/IGNITE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18095946#comment-18095946
]
Anton Vinogradov commented on IGNITE-627:
-----------------------------------------
[Ignite PR Checker|https://ignite-pr-checker.is-a.dev/?pr=13316] verdict for PR
13316 · RunAll build [9205244|https://ci2.ignite.apache.org/build/9205244] ·
147 suites ran, 0 reused
(!) *1 broken suite(s)* (failed without a reliable run):
- Platform C++ CMake (Win x64 | Release): Number of tests 595 is 43% less than
1046 in build #18136
(/) No test blockers otherwise; 24 pre-existing/flaky filtered out.
⏳ _Auto re-run *#1* in progress — 1 broken suite(s) re-queued (attempt 1/2), *≈
settled by 20:28 MSK*. This comment updates when they settle._
> Inconsistent value in near cache
> --------------------------------
>
> Key: IGNITE-627
> URL: https://issues.apache.org/jira/browse/IGNITE-627
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Reporter: Semen Boikov
> Assignee: Semen Boikov
> Priority: Major
> Labels: MakeTeamcityGreenAgain, ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This scenario is possible in atomic cache with near cache enabled:
> - key is updated concurrently from near and primary node
> - primary node first executes update request from near node, registers it as
> reader and sends GridNearAtomicUpdateResponse to near node
> - then primary node executes second update, sees that there is a reader and
> sends GridDhtAtomicUpdateRequest to near node
> - GridDhtAtomicUpdateRequest is handled first on near node (see
> GridNearAtomicCache.processDhtAtomicUpdateRequest), it tries to peek entry,
> it is not created yet and it is considered as evicted, updated is skipped and
> reader will be removed on primary node
> - then near node handles GridNearAtomicUpdateResponse and creates entry with
> incorrect value
> Tests
> GridCacheValueConsistencyAtomicPrimaryWriteOrderNearEnabledSelfTest.testPutRemoveConsistencyMultithreaded
> and testPutConsistencyMultithreaded fail from time to time because of this
> issue.
> Most probably there is similar issue in transactional cache since
> GridCacheValueConsistencyTransactionalNearEnabledSelfTest also fails from
> time to time.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
