[
https://issues.apache.org/jira/browse/IGNITE-12746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17056744#comment-17056744
]
Ignite TC Bot commented on IGNITE-12746:
----------------------------------------
{panel:title=Branch: [pull/7507/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5115514&buildTypeId=IgniteTests24Java8_RunAll]
> Regression in GridCacheColocatedDebugTest: putAll of sorted keys causes
> deadlock
> --------------------------------------------------------------------------------
>
> Key: IGNITE-12746
> URL: https://issues.apache.org/jira/browse/IGNITE-12746
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Reporter: Ilya Kasnacheev
> Assignee: Ivan Rakov
> Priority: Blocker
> Fix For: 2.8.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> After this commit:
> 7d4bb49264b IGNITE-12329 Invalid handling of remote entries causes partition
> desync and transaction hanging in COMMITTING state.
> the following tests:
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedColocated
> org.apache.ignite.internal.processors.cache.distributed.dht.GridCacheColocatedDebugTest#testPutsMultithreadedMixed
> started to be flaky because their ordered putAll operations started
> deadlocking.
> This is a regression compared to 2.7 and should be fixed, since it may affect
> production clusters.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
