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

[Backport MB-39067 to 6.0.5] Index creation may fail in case of one or more watchers are not available

    XMLWordPrintable

Details

    • Untriaged
    • 1
    • Unknown

    Description

      On GSI client, if WatchMetadata doesn't succeed for a subset of indexer nodes, the prepare create request and commit request will be sent only to the available watchers. But the planner considers all available indexer nodes for planning. If planner decides to put the index on the node for which watcher was not available, the index creation may fail.

      Attachments

        Issue Links

          For Gerrit Dashboard: MB-40410
          # Subject Branch Project Status CR V

          Activity

            Verified on 6.0.5-3332 with the above given steps.

            mihir.kamdar Mihir Kamdar (Inactive) added a comment - Verified on 6.0.5-3332 with the above given steps.

            Build couchbase-server-6.0.5-3327 contains indexing commit d3dbc8e with commit message:
            MB-40410: Fix index creation if one of the indexer nodes is not connected

            build-team Couchbase Build Team added a comment - Build couchbase-server-6.0.5-3327 contains indexing commit d3dbc8e with commit message: MB-40410 : Fix index creation if one of the indexer nodes is not connected

            QE Testing:

            1. Setup a cluster n1: kv, n1ql, index AND n2: index
            2. Rebalance.
            3. Create 1 index on node n1.
            4. Drop all incoming packets for n2:9100.
            5. Restart cbq-engine node on n1.
            6. Create an index.

            Before fix: Planner considers both nodes n1 and n2 for placement.
            After fix: Planner considers only n1 for placement as n2 is not reachable at the time.

            amit.kulkarni Amit Kulkarni added a comment - QE Testing: 1. Setup a cluster n1: kv, n1ql, index AND n2: index 2. Rebalance. 3. Create 1 index on node n1. 4. Drop all incoming packets for n2:9100. 5. Restart cbq-engine node on n1. 6. Create an index. Before fix: Planner considers both nodes n1 and n2 for placement. After fix: Planner considers only n1 for placement as n2 is not reachable at the time.

            People

              amit.kulkarni Amit Kulkarni
              amit.kulkarni Amit Kulkarni
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty