[
https://issues.apache.org/jira/browse/IGNITE-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Chugunov resolved IGNITE-8853.
-------------------------------------
Resolution: Duplicate
Fix Version/s: 2.7
> Test CacheSerializableTransactionsTest#testIncrementTxRestart fails on TC
> -------------------------------------------------------------------------
>
> Key: IGNITE-8853
> URL: https://issues.apache.org/jira/browse/IGNITE-8853
> Project: Ignite
> Issue Type: Bug
> Components: general
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> Test started to fail after implementing IGNITE-8657.
> There is the following message in logs that makes it clear what happens:
> {noformat}
> 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]]
> {noformat}
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
