[
https://issues.apache.org/jira/browse/IGNITE-7648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Voronkin updated IGNITE-7648:
-----------------------------------
Description:
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 default.
We decided to change timeout logic in case of failure detection enabled. We
start performing connect and handshake from 500ms increasing using exponential
backoff strategy.
was:
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 default.
> Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.
> -----------------------------------------------------
>
> 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 default.
> We decided to change timeout logic in case of failure detection enabled. We
> start performing connect and handshake from 500ms increasing using
> exponential backoff strategy.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
