Uploaded image for project: 'Jackrabbit Oak'
  1. Jackrabbit Oak
  2. OAK-2739

take appropriate action when lease cannot be renewed (in time)

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.2
    • 1.3.4, 1.4
    • core

    Description

      Currently, in an oak-cluster when (e.g.) one oak-client stops renewing its lease (ClusterNodeInfo.renewLease()), this will be eventually noticed by the others in the same oak-cluster. Those then mark this client as inactive and start recoverying and subsequently removing that node from any further merge etc operation.

      Now, whatever the reason was why that client stopped renewing the lease (could be an exception, deadlock, whatever) - that client itself still considers itself as active and continues to take part in the cluster action.

      This will result in a unbalanced situation where that one client 'sees' everybody as active while the others see this one as inactive.

      If this ClusterNodeInfo state should be something that can be built upon, and to avoid any inconsistency due to unbalanced handling, the inactive node should probably retire gracefully - or any other appropriate action should be taken, other than just continuing as today.

      This ticket is to keep track of ideas and actions taken wrt this.

      Attachments

        1. OAK-2739.patch
          15 kB
          Stefan Egli

        Issue Links

          blocks

          New Feature - A new feature of the product, which has yet to be developed. OAK-2844 Introducing a simple document-based discovery-light service (to circumvent documentMk's eventual consistency delays)

          • Major - Major loss of function.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. SLING-4603 discovery.oak: oak-based discovery implementation

          • Major - Major loss of function.
          • Closed
          is blocked by

          Improvement - An improvement or enhancement to an existing feature or task. OAK-2681 Update lease without holding lock

          • Major - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. OAK-2682 Introduce time difference detection for DocumentNodeStore

          • Major - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. OAK-3390 Avoid instanceof check in DocumentNodeStore

          • Major - Major loss of function.
          • Closed

          Test - A new unit, integration or system test. OAK-3236 integration test that simulates influence of clock drift

          • Major - Major loss of function.
          • Open
          relates to

          Improvement - An improvement or enhancement to an existing feature or task. OAK-3238 fine tune clock-sync check vs lease-check settings

          • Major - Major loss of function.
          • Closed

          Wish - General wishlist item. OAK-3250 Restart DocumentNodeStore on lease timeout instead of bundle.stop (was: System.exit)

          • Major - Major loss of function.
          • Open

          Activity

            People

              stefanegli Stefan Egli
              stefanegli Stefan Egli
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: