[IGNITE-6440] Flaky failures in DynamicColumnsAbstractConcurrentSelfTest

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Cannot Reproduce
• Affects Version/s: 2.3
• Component/s: sql
• Labels: MakeTeamcityGreenAgain sql-stability
• Assignee: Pavel Kuznetsov
• Reporter: Vladimir Ozerov
• Created: 19/Sep/17 13:54
• Updated: 25/Jul/19 07:19
• Resolved: 01/Apr/19 12:46

Description

Multiple failures are observed in concrete implementations of DynamicColumnsAbstractConcurrentSelfTest. Specifically:

testQueryConsistencyMultithreaded
testClientReconnect
testConcurrentRebalance 	
testCoordinatorChange
testConcurrentPutRemove

Apparently there are some bugs in the test itself, as the following root causes could be observed in logs:

junit.framework.AssertionFailedError: Found nodes from different clusters, probable some test does not stop nodes [allNodes=[index.DynamicColumnsConcurrentTransactionalReplicatedSelfTest3, index.DynamicColumnsConcurrentTransactionalReplicatedSelfTest2, index.DynamicColumnsConcurrentTransactionalReplicatedSelfTest1]]

Caused by: java.lang.NullPointerException: null
    at org.apache.ignite.internal.processors.cache.index.DynamicColumnsAbstractConcurrentSelfTest$3.call(DynamicColumnsAbstractConcurrentSelfTest.java:565)
    at org.apache.ignite.internal.processors.cache.index.DynamicColumnsAbstractConcurrentSelfTest$3.call(DynamicColumnsAbstractConcurrentSelfTest.java:560)
    at org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)

Please see TeamCity, history of "Queries 2" suite in master branch.

Issue Links

• links to: GitHub Pull Request #2758
• links to: GitHub Pull Request #2758