Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-27715

Support the ability for a ElasticSearch node to simply be a client and not store any data

    XMLWordPrintable

    Details

    • Type: Feature Request
    • Status: RESOLVED
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0
    • Fix Version/s: 11.0
    • Component/s: Search
    • Labels:
    • 10 status:
      Please Merge
    • Previous Issue Keys:
      SRCH-114

      Description

      see SRCH-113.

      The legacy search allowed certain nodes to be clients whereas other nodes peformed the actual indexing and searching work. ES supports this very same concept. As discussed here:
      http://www.elasticsearch.org/guide/reference/java-api/client.html

      If we simply want Sakai to only be a client to an external ES cluster, not store any data, but simply make remote calls for all ES work, that is as simple as just some extra config. This will still mean the Sakai cluster owns the indexing work to load things into ES, it just won't have to do the actual ES work in terms of storage or responding to search queries. In a large organization, that might be using ES for other purposes this is reasonable architecture. In addition, it takes the burden off the Sakai nodes to do searches and lowers the risk of something going bad with ES bringing down Sakai nodes.

      This also gives smaller installations a way have a single sakai node serve search requests, or in the case of Sakai hosting provider, they might have one ES cluster that services multiple Sakai installations.

      To tell any one single Sakai node to not store data simply do this:
      clientNode@org.sakaiproject.search.elasticsearch.ElasticSearchService=true

      To set the cluster name you would do:
      elasticsearch.cluster.name=my_awesome_es_cluster_that_rules_the_world

      unicast, multicast and all the other normal ES settings are not affected by this change. Those would still need to be configured to point to where ever the ES cluster lives.

        Gliffy Diagrams

          Zeplin

            Attachments

              Issue Links

                Activity

                  People

                  Assignee:
                  jbush John Bush
                  Reporter:
                  jbush John Bush
                  Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                    Dates

                    Created:
                    Updated:
                    Resolved:

                      Git Integration