Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-7648

Fix IGNITE_ENABLE_FORCIBLE_NODE_KILL system property.

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 2.3
    • 2.8
    • None
    • None

    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.

       

       

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            voropava Pavel Voronkin
            ascherbakov Alexey Scherbakov
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment