Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-31805

Index information is not updated on UI when some of the index nodes are not responsive

    XMLWordPrintable

Details

    • Untriaged
    • Unknown

    Description

      Steps to repro:

      a. Setup a cluster with 2 KV+Query and 3 indexer nodes

      b. Load sample buckets and create indexes

      c. Stop one of the indexer service

      d. Create a new index

       

      The newly created index is not seen on the UI. The issue can also be seen with the following steps:

      a. Setup a cluster with 2 KV+Query and 3 indexer nodes

      b. Load sample buckets and create indexes

      c. Stop all the 3 indexer nodes

      d. Bring back 2 of the indexer nodes

      e. The UI does not show any indexes

       

      The reason behind such an inconsistency is because, the "getIndexStatus" request will collect index information from all the nodes and if there is a failed node in the quorum, it will return the HTTP response as "500-Internal server error" along with the list of indexes from active nodes. Also the "code" field in response JSON set to "error". Because of this, the UI is not updating the information although response contains indexes from active indexer nodes.

       

      Ideally, the expectation is that UI shows the indexes that are currently available and also show a warning like "the index information shown is not complete as some index nodes are not responsive"

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            varun.velamuri Varun Velamuri created issue -
            raju Raju Suravarjjala made changes -
            Field Original Value New Value
            Fix Version/s Mad-Hatter [ 15037 ]
            jeelan.poola Jeelan Poola made changes -
            Link This issue relates to CBSE-5976 [ CBSE-5976 ]
            jeelan.poola Jeelan Poola made changes -
            Description Steps to repro:

            a. Setup a cluster with 2 KV+Query and 3 indexer nodes

            b. Load sample buckets and create indexes

            c. Stop one of the indexer service

            d. Create a new index

             

            The newly created index is not seen on the UI. The issue can also be seen with the following steps:

            a. Setup a cluster with 2 KV+Query and 3 indexer nodes

            b. Load sample buckets and create indexes

            c. Stop all the 3 indexer nodes

            d. Bring back 2 of the indexer nodes

            e. The UI does not show any indexes

             

            The reason behind such an inconsistency is because, the "getIndexStatus" request will collect index information from all the nodes and if there is a failed node in the quorum, it will return the HTTP response as "500-Internal server error". Also the "code" field in response JSON set to "error". Because of this, the UI is not updating the information.

             

            Ideally, the expectation is that UI shows the indexes that are currently available and also show a warning like "the index information shown is not complete as some index nodes are not responsive"
            Steps to repro:

            a. Setup a cluster with 2 KV+Query and 3 indexer nodes

            b. Load sample buckets and create indexes

            c. Stop one of the indexer service

            d. Create a new index

             

            The newly created index is not seen on the UI. The issue can also be seen with the following steps:

            a. Setup a cluster with 2 KV+Query and 3 indexer nodes

            b. Load sample buckets and create indexes

            c. Stop all the 3 indexer nodes

            d. Bring back 2 of the indexer nodes

            e. The UI does not show any indexes

             

            The reason behind such an inconsistency is because, the "getIndexStatus" request will collect index information from all the nodes and if there is a failed node in the quorum, it will return the HTTP response as "500-Internal server error" along with the list of indexes from active nodes. Also the "code" field in response JSON set to "error". Because of this, the UI is not updating the information although response contains indexes from active indexer nodes.

             

            Ideally, the expectation is that UI shows the indexes that are currently available and also show a warning like "the index information shown is not complete as some index nodes are not responsive"
            deepkaran.salooja Deepkaran Salooja made changes -
            Labels RMS
            jeelan.poola Jeelan Poola made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            varun.velamuri Varun Velamuri made changes -
            Labels RMS RMS needs-qe
            jliang John Liang made changes -
            Assignee Varun Velamuri [ varun.velamuri ] John Liang [ jliang ]
            jliang John Liang made changes -
            Assignee John Liang [ jliang ] Rob Ashcom [ rob.ashcom ]
            deepkaran.salooja Deepkaran Salooja made changes -
            Labels RMS needs-qe RMS needs-qe secondary-index
            rob.ashcom Rob Ashcom made changes -
            Assignee Rob Ashcom [ rob.ashcom ] Pavel Blagodov [ pavel ]
            pavel Pavel Blagodov made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            pavel Pavel Blagodov made changes -
            Actual Start 2019-07-16 06:02 (issue has been started)
            pavel Pavel Blagodov made changes -
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Resolved [ 5 ]
            pavel Pavel Blagodov made changes -
            Actual End 2019-07-19 02:24 (issue has been resolved)
            r.kalyanasundaram Ramalingam Kalyanasundaram [X] (Inactive) made changes -
            r.kalyanasundaram Ramalingam Kalyanasundaram [X] (Inactive) made changes -
            r.kalyanasundaram Ramalingam Kalyanasundaram [X] (Inactive) made changes -
            r.kalyanasundaram Ramalingam Kalyanasundaram [X] (Inactive) made changes -
            r.kalyanasundaram Ramalingam Kalyanasundaram [X] (Inactive) made changes -
            r.kalyanasundaram Ramalingam Kalyanasundaram [X] (Inactive) made changes -
            VERIFICATION STEPS Reproduced the issue on build #1969 and verified the issue on build #3814.
            Screen shots are in the attachment.
            Status Resolved [ 5 ] Closed [ 6 ]
            simon.dew Simon Dew made changes -
            Link This issue relates to DOC-6180 [ DOC-6180 ]

            People

              pavel Pavel Blagodov
              varun.velamuri Varun Velamuri
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty