Blocker 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.