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

Pin async indexer on cluster leader

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

Details

    • Improvement
    • Status: Closed
    • Blocker
    • Resolution: Fixed
    • None
    • 1.7.14, 1.8.0
    • lucene
    • None

    Description

      Currently, async indexer creates some data locally to declare which index files have been deleted from the indexer. This information is used by active deletion's purge logic (to be invoked via jmx).

      Since, async indexer sets its task to scheduler to run as singleton on the cluster (not pinning to anywhere), then the active deletion jmx execution requires the knowledge where async indexer is scheduled.

      To avoid that uncertainty, it's better to instead pin the async indexer on cluster leader and document that active deletion jmx also needs to be invoked on cluster leader.

      Attachments

        Activity

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

          People

            catholicon Vikas Saurabh
            catholicon Vikas Saurabh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment