ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7648) Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
Date Wed, 06 Feb 2019 06:12:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761519#comment-16761519

Ignite TC Bot commented on IGNITE-7648:

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3004295&amp;buildTypeId=IgniteTests24Java8_RunAll]

> -----------------------------------------------------
>                 Key: IGNITE-7648
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7648
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.3
>            Reporter: Alexei Scherbakov
>            Assignee: Pavel Voronkin
>            Priority: Major
>             Fix For: 2.8
> IGNITE_ENABLE_FORCIBLE_NODE_KILL system property was introduced in IGNITE-5718 as a way
to prevent unnecessary node drops in case of short network problems.
> I suppose it's wrong decision to fix it in such way.
> We had faced some issues in our production due to lack of automatic kicking of ill-behaving
nodes (on example, hanging due to long GC pauses) until we realised the necessity of changing
default behavior via property.
> Right solution is to kick nodes only if failure threshold is reached. Such behavior
should be always enabled.
> UPDATE: During a discussion it was decided what the property will remain disabled by

This message was sent by Atlassian JIRA

View raw message