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

Represent in the documenttion affection of several node addresses on failure detection.

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

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Later
    • Affects Version/s: None
    • Fix Version/s: 2.10
    • Component/s: documentation
    • Labels:
    • Ignite Flags:
      Docs Required

      Description

      We should emphasize that TcpDiscoverySpi prolongs detection of node failure if several IP addresses are set. Actual failure detection delay is: failureDetectionTimeout * addressesNumber.

      "You should assing multiple addresses to a node only if they represent some real physical connections which can give more reliability. Several addresses prolong failure detection of current node. The timeouts and settings on network operations (failureDetectionTimeout(), sockTimeout, ackTimeout, maxAckTimeout, reconCnt) work per connection/address. The exception is connRecoveryTimeout.
      Example: if you have 3 ip addresses configured for a node, Tcp Discovery takes up to 'failureDetectionTimeout * 3 + connRecoveryTimeout' to detect failure of this node".

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              vladsz83 Vladimir Steshin
              Reporter:
              vladsz83 Vladimir Steshin

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment