You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Sorokin (JIRA)" <ji...@apache.org> on 2018/05/31 14:26:00 UTC
[jira] [Comment Edited] (IGNITE-8311)
IgniteClientRejoinTest.testClientsReconnectDisabled causes exchange-worker
to terminate via NPE
[ https://issues.apache.org/jira/browse/IGNITE-8311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16496627#comment-16496627 ]
Dmitriy Sorokin edited comment on IGNITE-8311 at 5/31/18 2:25 PM:
------------------------------------------------------------------
The root cause of this error is inconsistent state of GridAffinityAssignmentCache, which appears when main cycle of ExchangeWorker.body0() continue work on occuring of IgniteCheckedException (last catch block at the end of cycle).
Proposed solution - further throwing of catched exception, it will prevent going into inconsistent state of grid components.
However, some tests of starting grid with incorrect configuration will cause the jvm halt due to critical system error detected, but that issue should be fixed in -IGNITE-1094-.
was (Author: cyberdemon):
The root cause of this error is inconsistent state of GridAffinityAssignmentCache, which appears when main cycle of ExchangeWorker.body0() continue work on occuring of IgniteCheckedException (last catch block at the end of cycle).
Proposed solution - further throwing of catched exception, it will prevent going into inconsistent state of grid components.
However, some tests of starting grid with incorrect configuration will cause the jvm halt due to critical system error detected, but that issue should be fixed in IGNITE-1049.
> IgniteClientRejoinTest.testClientsReconnectDisabled causes exchange-worker to terminate via NPE
> -----------------------------------------------------------------------------------------------
>
> Key: IGNITE-8311
> URL: https://issues.apache.org/jira/browse/IGNITE-8311
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.4
> Reporter: Andrey Kuznetsov
> Assignee: Dmitriy Sorokin
> Priority: Major
> Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Currently, tests use {{NoOpFailureHandler}} by default, hence this exchange-worker termination is masked. We are to fix it: test code should not be able to terminate system-critical thread.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)