Vikas Saurabh created OAK-7042:
----------------------------------

             Summary: Pin async indexer on cluster leader
                 Key: OAK-7042
                 URL: https://issues.apache.org/jira/browse/OAK-7042
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: lucene
            Reporter: Vikas Saurabh
            Assignee: Vikas Saurabh


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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to