Rebuilds are not simultaneously sent to each of the HA Search Services. Instead, rebuilds are accomplished using a single web-app node and the resulting rebuild activities are delivered to a single Search Service. If the web-app or the search service fails during a rebuild, the rebuild will have to be restarted from the beginning. You can control which Search Service is responsible for receiving rebuilds via the Service Directory configuration. The next three diagrams show how to accomplish a successful rebuild.
Note that if the document conversion node is running during a search index rebuild,
the web app nodes may be more responsive to requests due to reduced loads, but the
duration of the rebuild will be increased.
-
Initiate a Search rebuild from the Admin Console (). The rebuild activities will go to the Search Service configured
in the Service Directory. Wait for the rebuild to complete. Here's what happens
during this process:
- Shut down the Ingress Replicators with /usr/local/jive/services/ingress-replicator-service stop. (Note that you must be logged in as the jive user to successfully execute this and the other commands listed here). Activities that the Replicator Service has not delivered will be delivered after the restart. While the Ingress Replicators are offline, the web application will journal activities to disk. After the Ingress Replicator service is restarted, these journalled activities will be delivered to the Ingress Replicators.
- Shut down Search Service 2 (/usr/local/jive/services/search-service stop).
- Copy the active index from Search Service 1 to Search Service 2.
-
Restart Search Service 2 (/usr/local/jive/services/search-service start). This process
looks something like this:
-
Restart Ingress Replicators 1 and 2 (/usr/local/jive/services/ingress-replicator-service start).
