Solr Upload Existing Collection Config to Zookeeper

Walkthrough: Using SolrCloud for xConnect search

Abstract

A guide to using SolrCloud for xConnect search.

This topic describes how to configure SolrCloud as the search provider for xConnect search. You must configure the following roles and environments:

• xConnect Collection Search service

• xConnect Search Indexer

• Standalone developer environments (XP Single) that combine xConnect Collection Search and xConnect Search Indexer

Note

If you configure SolrCloud for a standalone developer environment (XP Single), you must still configure the xConnect Search Indexer separately. The indexer is a Windows Service or, in Azure, a Web Job. By default, it is nested in the root of the xConnect Drove Search service part.

You tin also configure SolrCloud for content search.

In social club to use SolrCloud for xConnect search, yous must create a SolrCloud farm and configure xConnect.

This walkthrough describes how to:

• Install Solr

• Upload the Solr configuration to Zookeeper

• Create an xDB collection

• Create aliases

• Configure xConnect to employ SolrCloud

Follow the instructions on the Solr website to install Solr and create a scaled surround, using ii or more Solr nodes with 1 or more external Zookeeper services. The following descriptions assume that you have a simple cluster with ane Zookeper service and two Solr nodes placed behind a load balancer.

Of import

Sitecore'southward SolrCloud configuration requires a load balancer. xConnect is secure by default and assumes that you lot accept enabled Solr SSL.

Nosotros recommend that you configure your load balancer to check that all Solr nodes are available and that they return the OK status code. Refer to Solr's ping documentation for more data.

For example, if you have two nodes behind a load balancer, check the following endpoints:

• https://<solr-node-i>/solr/xdb/admin/ping

• https://<solr-node-ane>/solr/xdb_rebuild/admin/ping

• https://<solr-node-2>/solr/xdb/admin/ping

• https://<solr-node-ii>/solr/xdb_rebuild/admin/ping

To upload the Solr configuration to Zookeper:

1. Open up a PowerShell panel and navigate to the <solr_root> binder.

2. In the panel, enter the following command:

   solr zk upconfig -d _default -n xdb -z <ZOOKEEPER_URL>"

You have now prepared the Solr configuration, and you can now create the xDB drove.

To create an xDB drove:

1. In the Solr administration UI, go to the Collections page using i of the nodes you created.

2. Click Add Collection.

3. Create a collection named xdb_internal . Use the xDB config set and specify other settings as shown:

   

4. Create a second collection named xdb_rebuild_internal with the same settings.

Refer to the SolrCloud documentation for information virtually collections, replicas, and shards.

To create aliases for your collections:

1. In the Solr administration UI, go to the Collections page using 1 of the nodes you created.

2. Click Create Alias.

3. Create an alias named xdb_rebuild and in the Collections list, click xdb_rebuild_internal .

3. Create a second alias named xdb and select xdb_internal in the Collections list.

4. To see a list of all aliases, use the URL https://<solrurl>/solr/admin/collections?activity=LISTALIASES.

5. Apply the schema modifications from the <xconnect-root>\App_Data\solrcommands\schema.json file to both collections using the Solr Schema API.

Note

You must utilize xdb and xdb_rebuild in your connection strings, not xdb_internal and xdb_rebuild_internal . xdb and xdb_rebuild are the default names of the primary and secondary indexes. If you modify the names of the indexes, you must update all connection strings.

Note

Do non give a collection and an allonym the same proper name.

You have now created a SolrCloud subcontract. Before y'all tin use it with xConnect, you must configure the xConnect roles to utilise SolrCloud.

Y'all must configure the xConnect connexion to the SolrCloud load balancer, which handles the fail-over for the Solr nodes.

Note

This example assumes that you have set up SSL.

To configure xConnect to use SolrCloud:

1. For every case of the xConnect Collection Search part, open the <office-root>\App_Config\ConnectionStrings.config file, specify the value of the solrCore connection cord, and add together the parameter solrCloud=true. For example:

   <add name="solrCore" connectionString="https://<loadbalancer>:8999/solr/xdb;solrcloud=true"/>                  

2. For every instance of the xConnect Search Indexer part, open the <part-root>\App_Config\ConnectionStrings.config file, specify the value of the solrCore connectedness cord, and add the parameter solrCloud=true. For case:

   <add name="solrCore" connectionString="https://<loadbalancer>:8999/solr/xdb;solrcloud=truthful"/>                  

   Note

   By default, the xConnect Search Indexer is located in the xConnect Collection Search service role, in the <role-root>\App_data\jobs\continuous\IndexWorker folder.

3. If you drift an existing deployment from Solr to SolrCloud you must rebuild the index. New deployments do not require this step.

williamssligized.blogspot.com

Source: https://doc.sitecore.com/xp/en/developers/91/platform-administration-and-architecture/walkthrough--using-solrcloud-for-xconnect-search.html

Share this post