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

Ignite cluster falls apart if two nodes segmented sequentially

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Blocker
    • Resolution: Fixed
    • 2.9
    • 2.9.1
    • None
    • None
    • Fixed processing of connection recovery timeout in TcpDiscoverySpi. If node loses connection, now it strictly obtains new connection to the ring or becomes segmented within this timeout.

    Description

      After [1] sequential nodes failure leads to segmentation of other nodes in the cluster. Reproducer attached.

      This ticked contains:

      • Reverted [1].
      • Fix for [1] to avoid the noted segmenttion.
      • Reverted [2] which depends on [1].

      [1] IGNITE-13134
      [2] IGNITE-13208

      Attachments

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

          People

            vladsz83 Vladimir Steshin Assign to me
            alex_pl Aleksey Plekhanov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 3h
              3h

              Slack

                Issue deployment