Single node re-indexing
The repotools reindex command can re-index a stand-alone Jazz server, or a server node in a cluster environment. For the latter, the server must be temporary isolated from the cluster for the maintenance duration. To accomplish this, you must first disable the server in the load balancer to avoid request being dispatched to this node during the shut down operation, and then stop the server.
Full cluster re-indexing
To perform a full cluster re-indexing, the reindex command must be issued on an isolated node as explained above. Using the "cluster" parameter, the command is then propagated to all the nodes in the cluster. The running servers perform the operation immediately depending on the state of its indexing service (activated or not), or like any other stopped server during the next start up.
repotools -reindex scope=search cluster
repotools -reindex scope=search
For the running servers, the re-indexing progress can be tracked by accessing https://{JazzServerURL}/jazz/indexing, where {JazzServerURL} is either a single node URL that tracks a specific server, or the cluster URL that aggregates all the nodes re-indexing activities into one result.
| Attribute | Description | Required | Default |
|---|---|---|---|
| teamserver.properties | Path to the teamserver.properties file. | Yes | conf/jazz/teamserver.properties |
| scope | The scope of reindexing. Values are all, query, and search. | Yes | all |
| cluster | Reindex all nodes in the cluster. | No | |
| contextPath | Repository context path. | No | /jazz |
| noPrompt | Do not prompt before reindexing a cluster. | No | |
| baseline | A comma separated list of baselines URI, without spaces. | No | none |
repotools -reindex teamserver.properties=conf/jazz/teamserver.properties scope=all