[IGNITE-8853] Test CacheSerializableTransactionsTest#testIncrementTxRestart fails on TC

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Fix Version/s: 2.7
• Component/s: general
• Labels: MakeTeamcityGreenAgain
• Assignee: Sergey Chugunov
• Reporter: Sergey Chugunov
• Created: 22/Jun/18 09:02
• Updated: 12/Dec/18 07:21
• Resolved: 17/Jul/18 08:49

Description

Test started to fail after implementing IGNITE-8657.

There is the following message in logs that makes it clear what happens:

junit.framework.AssertionFailedError: Unexpected exception [err=class org.apache.ignite.IgniteException: Node need try to reconnect [nodeId=5a7cfccb-d87e-4d2a-b044-f0a43e300006], cause=class org.apache.ignite.internal.IgniteNeedReconnectException: Node need try to reconnect [nodeId=5a7cfccb-d87e-4d2a-b044-f0a43e300006]]

IGNITE-8657 fixed issue with client nodes hanging when their initial ExchangeFutures were preempted from exchange queue on coordinator because of EXCHANGE_HISTORY setting.

It turned out that for some reason client may be instructed to reconnect even when it has already joined topology but now server node joining or leaving it.

Issue Links

• is part of: IGNITE-8905 Incorrect assertion in GridDhtPartitionsExchangeFuture
• links to: GitHub Pull Request #4275