If you have a high availability Lucene configuration, you can take one Lucene node out of service for maintenance while other Lucene nodes continue to operate. Then you can synchronize the out-of-date Lucene node with the current indexing data.
Log in to the Novell Vibe site as the Vibe administrator.
Take the Lucene node that needs maintenance out of service:
Click the
icon in the upper right corner of the page, then click the icon .Under
, click .In the list, locate the node that needs maintenance.
Make sure that
is selected.In the
box, change to .Click
, then click .The new setting is put into effect immediately, so that the Lucene node is no longer accessible to Vibe users.
Perform the needed maintenance on the Lucene server, then start the Lucene Index Server again.
Return the out-of-date Lucene node to full service:
Click the
icon in the upper right corner of the page, then click the icon .Under
, click .The out-of-date Lucene node is flagged with
.The catalina.out file, as described in Observing Lucene Node Activity
in Multi-Server Configurations and Clustering
in the Novell Vibe 3.3 Installation Guide, Vibe is not actually accessing the out-of-date Lucene node because it is out of sync with the Vibe site.
Select
, then click .The Deferred Update Log options disappear if the update is successful.
Click
.The Lucene node that was out of service has now been updated with current indexing data.