Common problems that real customers encounter in deploying SOLR search

The WebSphere http://www.aliyun.com/zixun/aggregation/3914.html ">commerce is run on a WebSphere creator Server with a high degree of scalability, Flexible Enterprise-class e-business applications. Since Version 7 Feature Pack 2, WebSphere Commerce has integrated SOLR search as its own search engine, providing more search-based enhancements, and later feature Pack 3,4,5 The new feature is further enhanced by the version. Now that more and more customers are enabling this new search engine functionality in a production environment and encountering a wide variety of issues, this article summarizes the general issues that real customers face in deploying SOLR search and provides the solution that this article is a best practice article that will give you the right to use SOLR Search customers and customers who will be using it to help.

Best Practices for building Indexes (build index) in the SOLR Search cluster environment

When you run the di-buildindex.bat/sh command on the WebSphere Commerce master to build the index, it executes according to the following logic:

Note: A little bit of WebSphere Commerce Feature Pack 2 is required, and the Feature table will be used using srchconf tables, WebSphere Commerce srchconfext Pack 3, and later versions.

In Figure 1, SOLR applies servers 1, 2, and 3 to form a clustered environment. If you use the default setting without making any modifications, the build index host is a SOLR Web server, which will cause a problem, and the SOLR Web server will forward the request for the index to any one of the application servers in the cluster via plugin, possibly SOLR application server 1 or SOLR Application server 2 or SOLR application Server 3.

This is inconsistent with the customer's general expectations. Customers typically take one member of a cluster (such as SOLR Application server 1) as a dedicated build index host, and other cluster members do not need to build the index, but instead use index replication (SOLR index Replication) technology to synchronize the index from the build index host.