is tooling can now be used by Support and the System Administrator to determine quickly which indexes are corrupt and then reindex them.
For diagnosing some of the cases around query performance Adobe often required existing index definition, index related statistics from the customer setup. So far this information was scattered across multiple resources. To make troubleshooting easier, Adobe has created tooling that will:
- Dump all index definition present on the system in a signle JSON file;
- Dump important statistics from existing indexes;
- Dump index contents for offline analysis;
- Will be usable even if AEM is not accessible
The above operations can now be done via the following operation index commands:
- --index-info - Collects and dumps various statistics related to the indexes
- --index-definitions - Collects and dumps index definitions
- --index-dump - Dumps index content
See below an example of how the commands work in practice:
1
| java -jar oak-run*.jar index --fds-path= /path/to/datastore /path/to/segmentstore/ --index-info --index-definitions --index-dump |
The reports would be generated in indexing-result/index-info.txt and indexing-result/index-definitions.json
In addition same details are provided via the Web Console and would be part of the configuration dump zip. They can be accessed at the following location:
http://serverhost:serverport/system/console/status-oak-index-defn
No comments:
Post a Comment