[
https://issues.apache.org/jira/browse/IGNITE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18093508#comment-18093508
]
Ignite TC Bot commented on IGNITE-627:
--------------------------------------
{panel:title=Branch: [pull/13316/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13316/head] Base: [master] : New Tests
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Cache 11{color} [[tests
5|https://ci2.ignite.apache.org/viewLog.html?buildId=9172879]]
* {color:#013220}IgniteCacheTestSuite11:
IgniteCacheAtomicProtocolTest.testNearEntryUpdateRacePutAll - PASSED{color}
* {color:#013220}IgniteCacheTestSuite11:
IgniteCacheAtomicProtocolTest.testNearEntryUpdateRaceInvoke - PASSED{color}
* {color:#013220}IgniteCacheTestSuite11:
IgniteCacheAtomicProtocolTest.testNearEntryUpdateRacePut - PASSED{color}
* {color:#013220}IgniteCacheTestSuite11:
IgniteCacheAtomicProtocolTest.testNearEvictionPolicyOnUpdates - PASSED{color}
* {color:#013220}IgniteCacheTestSuite11:
IgniteCacheAtomicProtocolTest.testNearEntryUpdateRacePutIfAbsent - PASSED{color}
{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9173017&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9173017
rerunBuildIds=none{color}
> 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
> 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)
