Reducing downtime during Lifecycle Query Engine reindexing
When you reindex Lifecycle Query Engine, reports that run during the reindexing
might not be accurate. Team members must run reports only after the reindexing is complete. To
reduce this downtime while you reindex Lifecycle Query Engine, you can clone the Lifecycle Query Engine instance and reindex the clone. Team members can continue to run reports and
historical trend data is still collected. After the clone is reindexed, you can merge the indexed
data and resume by using the original Lifecycle Query Engine instance.