nit0906 opened a new pull request, #1522: URL: https://github.com/apache/jackrabbit-oak/pull/1522
For scenarios where the async indexing lanes might be lagging for a large amount of time (let's assume days) and it might not be possible for the lane to catchup normally on it's own due to - 1. Large content diff to process leading to OOM and continuous failed async cycles 2. Possibility of old reference checkpoint no longer being present in the system and the async lane thus doing a complete reindex of the whole repo. In such cases, it might be required to make the async lane think that it is up to date by setting it's reference checkpoint to a more recent one. This PR introduces a jmx function to - 1. Pause and Abort the lagging async lane 2. Clear it's lease 3. Create a new checkpoint 4. Set the new checkpoint as reference checkpoint for the lane 5. delete the old checkpoint 6. resume the async indexing on the lane. If this operation is performed the async lane should start async indexing from the newly created checkpoint. But the diff of the content that was missed would need to be reindexed separately using oak-run's offline reindexing. To prevent unintentional misuse of this function, 1. It will specifically ask the user to enter "CONFIRM" before proceeding so that the user knows what he is doing. 2. It will not skip in case the lane on which it is called is not failing. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jackrabbit.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
