The SolrCloud Search Service Adapter connects the Intershop Commerce Management (ICM) with a Solr server that runs in cloud mode. It replaces the Solr search service adapter delivered with the ICM release and uses a more recent version of Solr and its features. The search index configuration and maintenance in the ICM back office is almost the same but uses the Schema- and ConfigSet-REST-APIs provided by the newer Solr server version. Thus, the Solr Server is separated and independent of the ICM application server cluster.
|Intershop Commerce Management||SolrCloud Search Service Adapter||Solr Server|
|7.10.10+||2.0.3 - 2.1.2||8.2.x|
|7.10.10+||2.2.1||8.2 to 8.6.2|
|7.10.23+ - 188.8.131.52+||2.3.4||8.2 to 8.7.0|
Solr 8.8.* does not work with the adapter yet. There is an issue with the configuration Set Backup/Restore that prevents a successful replication of configuration changes. In 8.8.0 there is a backward compatibility issue with SolrJ, see SOLR-15145. Solr 8.6.3/Solr 8.7 requires additional configuration, see ISSEA-167.
Listed Solr server versions were tested to work with the listed SolrCloud Adapter version. In general, minor and patch version upgrades of the Solr server are usually compatible with the adapter.
The following table lists the cartridges contained in the SolrCloud Adapter:
|ac_solr_cloud||The main implementation cartridge of the adapter defining and registering the search service.|
|ac_solr_cloud_bo||Additional functionality for the Commerce Management application. It provides additional configuration options for the index management, especially for suggest and spell-check.|
|solrcloud_config||Additional configuration to be deployed to share.|
The cartridges need to be deployed as a replacement of the Solr cartridges delivered by default (ac_search_solr, ac_search_solr_bo). These are part of the ICM component set f_business or (better to say) intershop7 assembly. Starting with ICM version 184.108.40.206, the Responsive Starter Store is preconfigured to use the SolrCloud Search Service Adapter by default. Please see the Cookbook - Deployment of Solr Search Adapters on how to setup your project using ICM 220.127.116.11 and higher. For previous ICM versions please follow the Recipe - Setup project using Solr Cloud. The deployment of the SolrCloud Adapter 2.0.0 requires additional deployment of
solrcloud_config. Add the
'com.intershop.solrcloud:solrcloud_config' line to the includes of the share host type.
The SolrCloud Search Service Adapter requires a Solr server that runs in cloud mode. Please see the Guide - Deployment Solr Cloud Server on how to setup a Solr server for development or production. This guide also provides information on how to configure ICM to use a Solr server.
The data replication of indexes has changed with this adapter implementation. The standard ICM file replication is not used anymore to replicate the index data. Instead, the adapter comes with its own replication decorator that uses the backup/restore collection API functionality of Solr. Please see Guide - Solr Replication for the description and configuration of the index replication with the SolrCloud server.
Data replication with a Solr Cloud cluster requires to mount a shared file system at the same path on each Solr node. The ICM must configure the property
solr.cloudBackupLocation to point to this shared location.
The base ICM version of the adapter is now 18.104.22.168 The adapter is built and tested with this version. Thus it is recommended to update ICM 22.214.171.124 or higher to use this adapter.
With reworking the SolrCloudClient caching to use a single client object, the following changes were required. Custom code based on these classes must be changed:
get(Domain domain, String indexName, String node)Always use the added method
com.intershop.adapter.search_solr.server.Serverwas moved to
QueryResponse queryResponse = provider.get(idx).query(solrQuery, METHOD.POST);
String collectionName = SolrCollectionAdmin.getCollectionName(idx.getDomain().getDomainName(), idx.getIndexID()); QueryResponse queryResponse = provider.get().query(collectionName, solrQuery, METHOD.POST);
BackupAndRestoreSolrCloudIndexesDecorator was changed:
The deprecated method
com.intershop.adapter.search_solr.server.staging.BackupAndRestoreSolrCloudIndexesDecorator#readAndInstantiateSearchIndexesOfSite(Domain site) is removed.
BackupAndRestoreSolrCloudIndexesDecorator keeps track of the backed up edit system indexes now. Indexes that are deleted in the edit system are not available in the backup anymore and will be deleted in the live system as well. In addition, the restored collections are now checked to contain the document count of the backup. The respective methods for restoring the index in the decorator and in the
com.intershop.adapter.search_solr.server.impl.SolrCollectionAdmin do have an additional parameter
expectedNumFound and old restore methods are deprecated now. (ISSEA-155)
The Solr Server version 8.6.0 in conjunction with data replication requires to set the backup location as an allowed path for the Solr server cluster. You can specify the allowed paths by setting a system property via environment in the startup script:
Please see also the respective Solr Upgrade Notes.
|ISSEA-132||Replace DELETE Method Workaround from Solr Server Implementation|
|ISSEA-127||Replace PhantomJS for Geb Tests with GeckoDriver|
|ISSEA-123||Verify Backup of SolrCloud Indexes Directory Structure during Replication|
|ISSEA-120||Update SolrJ to 8.4.1 - Update Solr Configuration|
|ISSEA-81||Remove Switch for Old Solr Core API|
|ISSEA-138||Selected Filter Entry with No Values in the Result has HitCount of 1|
|ISSEA-135||UTF-8 Characters (e.g. Umlauts) are Not Correctly Encoded for Synonyms/Stop Words|
|ISSEA-131||Solr Communication - AlreadyClosedException|
|ISSEA-128||Storefront Load test with 3 Application Servers Leads to Many Exceptions|
|ISSEA-121||Undo Replication Fails with Exception|
|ISSEA-119||Remove Unsupported Rollback Call|
The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Web site, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.