How to re-index existing indexes¶
Note
For technical resons, certain indexes cannot be re-indexed. If such indexes are created with an old version that is no longer supported by a new Elasticsearch version, the only way to handle these indexes for update is deleting them.
Re-indexing is the way of converting old version indexes into the currrent version, i.e., v6 to v7. There is actually no need to do this, until Elasticsearch version 8 or later is supported by nJAMS, that then will no longer be capable of working with v6 indexes.
Re-indexing is very time and resources consuming, and you should evaluate whehter or not you need to do it.
Note
If you need to re-index Elasticsearch 5 indexes for updating to nJAMS Server 5.1, you need to do this with nJAMS Server 4.4 or 5.0. Please see the according documentation for details.
The following instructions describe re-indexation from v6 to v7.
Starting situation after upgrading your Elasticsearch Cluster from 6 to 7 and upgraded nJAMS Server to 5.1: | |||||||
---|---|---|---|---|---|---|---|
When upgrade is done and nJAMS Server is started again, you can enter the “Index Management” page to see the current state of your indexes of your Elasticsearch Cluster.
Go to
|
|||||||
Procedure for re-indexing: | |||||||
Caution Though possible, you should be very careful with running multiple re-indexing tasks at the same time, since re-indexing requires much resources in the Elasticsearch cluster. That also means, during re-indexing, the Elasticsearch cluster may become stressed. |