Switching to Elasticsearch for Orient Me

If indexing and retrieval for Orient Me Top Updates is being handled by Solr, switching to Elasticsearch is recommended when you upgrade to Component Pack 6.0.0.9.

About this task

To use Elasticsearch instead of Solr, you can either index both Elasticsearch and Solr for the first month, or just begin indexing with Elasticsearch.

Procedure

  1. Do one of the following to configure the indexing service:
    • To index both for one month (retrieval can still be from Solr):
      helm upgrade orientme extractedFolder/microservices_connections/hybridcloud/
      helmbuilds/orientme-0.1.0-20200321-174037.tgz \
      --set <args_from_orientme_upgrade>,\
      orient-indexing-service.indexing.solr=true,\
      orient-indexing-service.indexing.elasticsearch=true
      
    • To index only Elasticsearch going forward (retrieval will capture all but the last top update):
      helm upgrade extractedFolder/microservices_connections/hybridcloud/
      helmbuilds/orientme-0.1.0-20200321-174037.tgz \
      --set <args_from_orientme_upgrade>,\
      orient-indexing-service.indexing.solr=false,\
      orient-indexing-service.indexing.elasticsearch=true

      where <args_from_orientme_upgrade> is the same helm values that are used during the “Upgrading orientme” task in Upgrading Component Pack 6.5 to 6.5 CR1. Do not copy over the values for what is explicitly listed above; use the new values. If you don't specify these values, the helm upgrade will reset values to their default. You can determine the values used during the upgrade by running helm get values orientme.

  2. Once indexing to Elasticsearch is complete, configure the retrieval service to get Orient Me Top Updates from Elasticsearch instead of Solr:
    1. Run the following command:
      helm upgrade orientme extractedFolder/microservices_connections/hybridcloud/helmbuilds/orientme-0.1.0-20200321-174037.tgz \
      --set <args_from_step1_above>,orient-retrieval-service.retrieval.elasticsearch=true

      where <args_from_step1_above> is the same helm values that are used in the last step (either to index to both Solr and Elasticsearch, or to index only to Elasticsearch). If you don't specify these values, the helm upgrade will reset values to their default. You can determine the values used during the upgrade by running helm get values orientme .

    2. (Optional) Configure the following Elasticsearch setting if you want to change the default value of 3000. The setting controls how many pages of content can be displayed in Top Updates, and the default reflects a balance between content and performance. A higher value allows more pages to be displayed; a lower value improves performance. The formula for how many stacks are retrieved is (Page #) X (Stacks per page) = (# of stacks).
      orient-retrieval-service.retrieval.esStacksSizeLimit=<your value>
  3. Optional: If you want to switch back to using solr and zookeeper for Orient Me, run the following command:
    helm upgrade orientme extractedFolder/microservices_connections/hybridcloud/helmbuilds/orientme-0.1.0-20190329-081601.tgz \
    --set <args_from_initial_install>,orient-indexing-service.indexing.solr=true,\
    orient-indexing-service.indexing.elasticsearch=false,\
    orient-retrieval-service.retrieval.elasticsearch=false
    

    where <args_from_initial_install> is the same helm values that are set on the current installation. Do not copy over the values for what is explicitly listed above; use the new values. If you don't specify these values, the helm upgrade will reset values to their default. You can determine the values used during the initial install by running helm get values orientme.