[ https://issues.apache.org/jira/browse/IGNITE-12033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-12033: ------------------------------------ Comment: was deleted (was: {panel:title=Branch: [pull/8870/head] Base: [master] : Possible Blockers (27)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1} {color:#d04437}Cache (Restarts) 1{color} [[tests 9|https://ci.ignite.apache.org/viewLog.html?buildId=5910039]] * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllTenNodesTwoBackups - Test has low fail rate in base branch 0,0% and is not flaky * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutEightNodesTwoBackups - Test has low fail rate in base branch 0,0% and is not flaky * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxSixNodesTwoBackups - Test has low fail rate in base branch 0,0% and is not flaky * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackups - Test has low fail rate in base branch 0,0% and is not flaky * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutSixNodesTwoBackups - Test has low fail rate in base branch 0,0% and is not flaky * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxEightNodesTwoBackups - Test has low fail rate in base branch 0,0% and is not flaky * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxPutAllFourNodesTwoBackups - Test has low fail rate in base branch 0,0% and is not flaky * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithTxFourNodesOneBackupsOffheapEvict - Test has low fail rate in base branch 0,0% and is not flaky * IgniteCacheRestartTestSuite: GridCacheReplicatedNodeRestartSelfTest.testRestartWithPutFourNodesOneBackupsOffheapEvict - Test has low fail rate in base branch 0,0% and is not flaky {color:#d04437}Control Utility{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5910080]] {color:#d04437}Basic 1{color} [[tests 12 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5910026]] * IgniteBasicTestSuite: GridUnsafeDataOutputArraySizingSelfTest.testChanged2 - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureIgniteException - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListeners - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChain - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsyncOnError - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListeners - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testFutureException - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testAsyncListenersOnError - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainAsync - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testChainError - Test has low fail rate in base branch 0,0% and is not flaky * IgniteBasicTestSuite: IgniteCacheFutureImplTest.testListenersOnError - Test has low fail rate in base branch 0,0% and is not flaky ... and 1 tests blockers {color:#d04437}ZooKeeper (Discovery) 3{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=5910068]] * ZookeeperDiscoverySpiTestSuite3: GridEventConsumeSelfTest.testResources - Test has low fail rate in base branch 0,0% and is not flaky {color:#d04437}Platform .NET (Core Linux){color} [[tests 1 TC_SERVICE_MESSAGE |https://ci.ignite.apache.org/viewLog.html?buildId=5910062]] * dll: ProjectFilesTest.TestAllCsharpFilesAreIncludedInProject - Test has low fail rate in base branch 0,0% and is not flaky {color:#d04437}Cache 3{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=5910044]] * IgniteBinaryObjectsCacheTestSuite3: GridCacheInterceptorTransactionalRebalanceTest.testPutIfAbsent - Test has low fail rate in base branch 0,0% and is not flaky {color:#d04437}[Build]{color} [[tests 0 Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=5928575]] {panel} {panel:title=Branch: [pull/8870/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1} {color:#00008b}Platform .NET (Core Linux){color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=5910062]] * {color:#013220}dll: CacheTestAsyncAwait.TestAsyncAwaitContinuationIsExecutedWithConfiguredExecutor - PASSED{color} {panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5928677&buildTypeId=IgniteTests24Java8_RunAll]) > Callbacks from striped pool due to async/await may hang cluster > --------------------------------------------------------------- > > Key: IGNITE-12033 > URL: https://issues.apache.org/jira/browse/IGNITE-12033 > Project: Ignite > Issue Type: Bug > Components: cache, platforms > Affects Versions: 2.7.5 > Reporter: Ilya Kasnacheev > Assignee: Pavel Tupitsyn > Priority: Critical > Labels: iep-70 > Fix For: 2.11 > > Time Spent: 10m > Remaining Estimate: 0h > > Discussed on dev-list: > http://apache-ignite-developers.2346864.n4.nabble.com/Re-EXTERNAL-Re-Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td42921.html > *Must use the public pool for callbacks as the most obvious step.* > ---- > http://apache-ignite-users.70518.x6.nabble.com/Replace-or-Put-after-PutAsync-causes-Ignite-to-hang-td27871.html#a28051 > There's a reproducer project. Long story short, .Net can invoke cache > operations with future callbacks, which will be invoked from striped pool. If > such callbacks are to use cache operations, those will be possibly sheduled > to the same stripe and cause a deadlock. > The code is very simple: > {code} > Console.WriteLine("PutAsync"); > await cache.PutAsync(1, "Test"); > Console.WriteLine("Replace"); > cache.Replace(1, "Testing"); // Hangs here > Console.WriteLine("Wait"); > await Task.Delay(Timeout.Infinite); > {code} > async/await should absolutely not allow any client code to be run from > stripes. -- This message was sent by Atlassian Jira (v8.3.4#803005)