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

Make AsynchIndexUpdate task to run only on a single node in a cluster

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

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.12
    • 0.13
    • core

    Description

      Currently the {{AsynchIndexUpdate }} job which performs the indexing in background is run on every node in a cluster. This at times causes commit failures when running Oak in a cluster using Mongo MK. As merging of indexed content say Lucene is tricky to implement it would be better to restrict this job to run as a singleton in a cluster

      See http://markmail.org/thread/qff2fj7nqtbuhr4i for more discussion

      Attachments

        Issue Links

        is related to

        Improvement - An improvement or enhancement to an existing feature or task. SLING-5387 Provide support for running singleton jobs on non leader cluster nodes also

        • Major - Major loss of function.
        • Closed

        Improvement - An improvement or enhancement to an existing feature or task. OAK-4563 Specify thread pool name which should be used by Async Indexing task

        • Minor - Minor loss of function, or other problem where easy workaround is present.
        • Closed

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

          People

            chetanm Chetan Mehrotra
            chetanm Chetan Mehrotra
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment