Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Provide support for out of band indexing where oak-run is connected in read only mode with NodeStore and indexes are stored on file system. These are then imported back by target system.
Had a discussion with catholicon and following flow was determined
- Admin would create provision a checkpoint via CheckpointMBean
- oak-run index is connected to NodeStore in read only mode and passed with
- checkpoint from previous step
- list of indexes which need to be reindexed
- oak-run index logic would then proceed with reindexing. However the created index data would be stored locally. This would make use of
- Once indexing is completed it would dump all index to an output folder with some metadata
- Then admin can copy this index data and use an MBean on the target setup to "import" it back. This import would need to
- Pause the current async indexers
- Import the external index files
- Bring the external indexer upto date to there respective lanes checkpoint
- Resume the async indexer
The benefit of this approach is that
- We only need to backport the import logic. Rest all can be implemented in trunk and need not be backported.
- Using read-only mode allow oak-run from trunk to be safely connected to any of the old versions
Attachments
Issue Links
- is blocked by
-
OAK-6249 FSDirectoryFactory to manage indexes on local file system
- Closed
- is related to
-
OAK-5970 (Re-)Indexing: estimate progress / ETA
- Closed
-
OAK-6353 Use Document order traversal for reindexing performed on DocumentNodeStore setups
- Closed
- relates to
-
OAK-6081 Indexing tooling via oak-run
- Closed