Updating the Solr configset

As updated versions of the Solr configset for your respective SaaS application become available to support Solr upgrades, you will need to update your Solr configset.

1. Connect to the target server using your preferred ssh tool (e.g., PuTTY) and log in.
2. Upload the new version of the Solr configset file to your target server.
   Note: For Microsoft 365 you will need to select the configset archive that corresponds to your Solr version.

   Configsets for Microsoft 365

   Solr version	Configset archive
   9.5.0	solr_o365_configset_v4.zip
   8.11.1	solr_o365_configset_v3.zip

3. Upgrading the Solr configset

   In the following example, version 4 of the configset for Microsoft 365 will be used.

   Note: This step only needs to be completed on one of the Solr Cluster nodes
   1. Upload the new solr_o365_configset_v4.zip configset to a Solr node and unzip its contents to a temporary folder:
      unzip -d /tmp/solr_o365_configset_v4 /tmp/solr_o365_configset_v4.zip
   2. Deploy the new configset to all nodes. The following ZooKeeper script will take the new configset and copy it to each Solr server of the deployment.

      /opt/solr/server/scripts/cloud-scripts/zkcli.sh -zkhost server1:2181,server2:2181,server3:2181 \
      -cmd upconfig -confdir /tmp/solr_o365_configset_v4 -confname eperi_o365

      Output upon success:

      INFO  - 2024-04-15 10:46:22.966; org.apache.solr.common.cloud.ConnectionManager; Waiting up to 30000ms for client to connect to ZooKeeper
      INFO  - 2024-04-15 10:46:23.010; org.apache.solr.common.cloud.ConnectionManager; zkClient has connected
      INFO  - 2024-04-15 10:46:23.010; org.apache.solr.common.cloud.ConnectionManager; Client is connected to ZooKeeper
      INFO  - 2024-04-15 10:46:23.120; org.apache.solr.core.NodeConfig; Loading solr.xml from SolrHome (not found in ZooKeeper)
      INFO  - 2024-04-15 10:46:23.121; org.apache.solr.core.SolrXmlConfig; Loading solr.xml from ./../../solr/solr.xml
      INFO  - 2024-04-15 10:46:23.169; org.apache.solr.common.cloud.ConnectionManager; Waiting up to 15000ms for client to connect to ZooKeeper
      INFO  - 2024-04-15 10:46:23.180; org.apache.solr.common.cloud.ConnectionManager; zkClient has connected
      INFO  - 2024-04-15 10:46:23.181; org.apache.solr.common.cloud.ConnectionManager; Client is connected to ZooKeeper

   3. Reload the collections.

      cd /opt/solr/server/etc
      # Reload the microsoft_teams collection
      curl -k -E server.cer.pem --key server.key.pem --user solr:<password> 'https://localhost:8983/solr/admin/collections?action=RELOAD&name=microsoft_teams'
      # Reload the o365 collection
      curl -k -E server.cer.pem --key server.key.pem --user solr:<password> 'https://localhost:8983/solr/admin/collections?action=RELOAD&name=o365'
      # Reload the o365_sharepoint collection
      curl -k -E server.cer.pem --key server.key.pem --user solr:<password> 'https://localhost:8983/solr/admin/collections?action=RELOAD&name=o365_sharepoint'

      Sample output for each reload:

      Enter PEM pass phrase:
      {
        "responseHeader":{
          "status":0,
          "QTime":13
        }
      }

   4. Restart the Solr service

      systemctl restart solr

   5. Optional: If Basic Authentication has just been configured, reconfigure the Solr services in eperi sEcure Platform, following Configuring the Solr services in eperi sEcure Platform
   You have successfully reuploaded the Solr configset with Basic Authentication.