Updating a Search Server Cluster
Updating a Search Server Cluster
- Halt any user updates to the system and ensure no changes via the Commerce Manager, Import/Export or Data Sync tool are in progress
- Ensure the indexing activity is complete for all indexes by checking the indexing status in CM's Configuration section under Search Indexes.
- Back up all existing indexes by calling the following links. These links will call the SOLR replication API:
http://master_host:port/searchserver/category/replication?command=backup http://master_host:port/searchserver/cmuser/replication?command=backup http://master_host:port/searchserver/customer/replication?command=backup http://master_host:port/searchserver/dynamicContentDelivery/replication?command=backup http://master_host:port/searchserver/product/replication?command=backup http://master_host:port/searchserver/promotion/replication?command=backup http://master_host:port/searchserver/shippingservicelevel/replication?command=backup http://master_host:port/searchserver/sku/replication?command=backup
- Disable replication on the slave servers by calling the following links. Make sure this is done for all slaves.
http://slave_host:port/searchserver/category/replication?command=disablepoll http://slave_host:port/searchserver/cmuser/replication?command=disablepoll http://slave_host:port/searchserver/customer/replication?command=disablepoll http://slave_host:port/searchserver/dynamicContentDelivery/replication?command=disablepoll http://slave_host:port/searchserver/product/replication?command=disablepoll http://slave_host:port/searchserver/promotion/replication?command=disablepoll http://slave_host:port/searchserver/shippingservicelevel/replication?command=disablepoll http://slave_host:port/searchserver/sku/replication?command=disablepoll
- Shut down, update, and restart the master search server:
- Shut down the application server.
- Redeploy the updated search server war.
- Restart the application server.Note:
If your search indexes are normally located within the searchserver/WEB-INF folder, you may need to restore them from your back up location or do a full rebuild
- Rebuild any indexes that would be affected by the update via the Commerce Manager. For step-by-step instructions on how to do this, see Requesting Search Index Rebuilds.
- Verify the master indexes. Since the master server is a full search instance, you can check its state by doing one of the following:
- Issuing manual SOLR queries.
- By redirecting Cortex server instance to point to the master instead of a slave.
- Do one of the following:
- If you are applying code updates to the slave servers, do the following for all slaves:
- Remove the slave from the search cluster.
- Shutdown the server.
- Redeploy the updated search server war.
- Restart the server. The restarted slave will immediately begin polling the master for index updates on startup.
- Restore the slave to the search cluster.
- If you are not updating the slave servers, resume index replication by calling the following links for all slaves:
http://slave_host:port/searchserver/category/replication?command=enablepoll http://slave_host:port/searchserver/cmuser/replication?command=enablepoll http://slave_host:port/searchserver/customer/replication?command=enablepoll http://slave_host:port/searchserver/dynamicContentDelivery/replication?command=enablepoll http://slave_host:port/searchserver/product/replication?command=enablepoll http://slave_host:port/searchserver/promotion/replication?command=enablepoll http://slave_host:port/searchserver/shippingservicelevel/replication?command=enablepoll http://slave_host:port/searchserver/sku/replication?command=enablepoll
- If you are applying code updates to the slave servers, do the following for all slaves: