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

Search tool displays all index workers in the cluster instead of just the configured service

    Details

    • Type: Bug
    • Status: Awaiting Review
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 12.6
    • Fix Version/s: None
    • Component/s: Search
    • Labels:
      None
    • Environment:
      Elasticsearch v1.7.5
      Sakai 12.x
    • Test Plan:
      Hide

      Please add a Test Plan here.

      Show
      Please add a Test Plan here.

      Description

      In Search > Admin view of the search tool, the Index Workers section displays all of the workers used instead of just the service configured.  If you use the same elastic search instance for other instances like dev, qa, and prod, you will see all of those listed regardless of the instance you are on.   Below is an example of the properties setup for a Dev, Test, Prod setup using the same elastic search server:

       

       

      DEV
      search.enable=true
      elasticsearch.http.enabled=false
      elasticsearch.cluster.name=ES-1.7.5
      elasticsearch.node.data=false
      elasticsearch.node.master=false
      elasticsearch.transport.tcp.port=38476
      elasticsearch.discovery.zen.ping.multicast.enabled=false
      indexName@org.sakaiproject.search.elasticsearch.ElasticSearchService=DEV
      indexName@org.sakaiproject.search.elasticsearch.ElasticSearchIndexBuilder=dev_sakai_index
      indexName@org.sakaiproject.samigo.search.QuestionElasticSearchIndexBuilder=dev_questions_index
      elasticsearch.discovery.zen.ping.unicast.hosts=es-01:38451,es-02:38451
      QA 
      search.enable=true
      elasticsearch.http.enabled=false
      elasticsearch.cluster.name=ES-1.7.5
      elasticsearch.node.data=false
      elasticsearch.node.master=false
      elasticsearch.transport.tcp.port=38486
      elasticsearch.discovery.zen.ping.multicast.enabled=false
      indexName@org.sakaiproject.search.elasticsearch.ElasticSearchService=QA
      indexName@org.sakaiproject.search.elasticsearch.ElasticSearchIndexBuilder=qa_sakai_index
      indexName@org.sakaiproject.samigo.search.QuestionElasticSearchIndexBuilder=qa_questions_index
      elasticsearch.discovery.zen.ping.unicast.hosts=es-01:38451,es-02:38451
      PROD
      search.enable=true
      elasticsearch.http.enabled=false
      elasticsearch.cluster.name=ES-1.7.5
      elasticsearch.node.data=false
      elasticsearch.node.master=false
      elasticsearch.transport.tcp.port=38496
      elasticsearch.discovery.zen.ping.multicast.enabled=false
      indexName@org.sakaiproject.search.elasticsearch.ElasticSearchService=PROD
      indexName@org.sakaiproject.search.elasticsearch.ElasticSearchIndexBuilder=prod_sakai_index
      indexName@org.sakaiproject.samigo.search.QuestionElasticSearchIndexBuilder=prod_questions_index
      elasticsearch.discovery.zen.ping.unicast.hosts=es-01:38451,es-02:38451
      

      These all use the same cluster name but have their own search service and indexes.  Sakai will display all of the worker threads in that cluster regardless of the ElasticSearchService configured.  So, in prod, you will also see the worker threads for DEV, QA, and any other instances configured to run on that elastic search cluster.  

       

      The ideal view would be to only display the worker threads configured for the search service (i.e only PROD see PROD threads.)

       

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                karagon Kenneth Aragon
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Git Source Code