You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Sergey Chugunov (JIRA)" <ji...@apache.org> on 2018/06/22 09:03:00 UTC
[jira] [Created] (IGNITE-8853) Test
CacheSerializableTransactionsTest#testIncrementTxRestart fails on TC
Sergey Chugunov created IGNITE-8853:
---------------------------------------
Summary: 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
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)