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

Query node not reachable after a bucket flush in test_couchbase_bucket_flush

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Critical
    • 4.0.0
    • 4.0.0
    • secondary-index
    • Security Level: Public
    • Build 4.0.0-2213
    • Untriaged
    • No

    Description

      Test case that is failing -
      ./testrunner -i /tmp/recoverytests-add-index.ini -t 2i.recovery_2i.SecondaryIndexingRecoveryTests.test_couchbase_bucket_flush,nodes_init=5,nodes_in=1,initial=,before=create_index,after=drop_index,groups=simple,dataset=default,doc-per-day=10,services_init=n1ql:kv-kv-kv-index-index,doc-per-day=50,standard_buckets=1,sasl_buckets=1,skip_build_tuq=True,cbq_version=sherlock,scan_consistency=request_plus,get-cbcollect-info=True

      Steps performed by the test -

      • Create three buckets bucket0, default,standard_bucket0
      • Create about 10 indexes in each bucket
      • Flush the three buckets
      • Create an index on bucket0 - this fails

      2015-06-01 11:35:52 | INFO | MainProcess | test_thread | [basetestcase.sleep] sleep for 3 secs. ...
      2015-06-01 11:35:59 | INFO | MainProcess | test_thread | [rest_client.flush_bucket] Flush for bucket 'bucket0' was triggered
      2015-06-01 11:36:05 | INFO | MainProcess | test_thread | [rest_client.flush_bucket] Flush for bucket 'default' was triggered
      2015-06-01 11:36:10 | INFO | MainProcess | test_thread | [rest_client.flush_bucket] Flush for bucket 'standard_bucket0' was triggered
      2015-06-01 11:36:10 | INFO | MainProcess | test_thread | [base_2i._set_query_explain_flags] {'in_between':

      {'query_explain_ops': False, 'create_index': False, 'drop_index': False, 'query_ops': False}

      , 'initial':

      {'query_explain_ops': False, 'create_index': False, 'drop_index': False, 'query_ops': False}

      , 'after':

      {'query_explain_ops': False, 'create_index': False, 'drop_index': True, 'query_ops': False}

      , 'before': {'query_explain_ops': False, 'create_index': True, 'drop_index': False, 'query_ops': False}}
      2015-06-01 11:46:39 | ERROR | MainProcess | Cluster_Thread | [rest_client._http_request] socket error while connecting to http://172.23.121.141:8093/query?statement=CREATE+INDEX+employeed0ba2c6644684606bbb3e33faba51feejob_title+ON+bucket0%28job_title%29+USING+GSI+ error timed out

      From query log, I dont see logs between 11:37:07 to 11:47:31.

      The create index is issued around 11:46:39.

      Nodes:
      [SERVER_1]
      ip:172.23.121.141
      services=n1ql,kv

      [SERVER_2]
      ip:172.23.121.142
      services=kv

      [SERVER_3]
      ip:172.23.121.143
      services=kv

      [SERVER_4]
      ip:172.23.121.144
      services=index

      [SERVER_5]
      ip:172.23.121.145
      services=index

      The logs from all five nodes are uploaded at: https://s3-ap-southeast-1.amazonaws.com/indexing-test/logs/Jenkins/Recovery_1/testrunner-15-Jun-01_11-20-53.tar.gz

      The test output is captured in testoutput.log file.

      Attachments

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

        Activity

          People

            deepkaran.salooja Deepkaran Salooja
            prathibha Prathibha Bisarahalli (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty