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

vbucket_seqno last_persisted_snap_start > last_persisted_seqno in hard failover case

    XMLWordPrintable

Details

    Description

      Build: 5.5.4 build 4340

      Scenario:

      1. Create 4node cluster
      2. Create "default" couchbase bucket
      3. Load initial data 1K
      4. Perform failover of node-2 using `stop couchbase server`
      5. Perform update operation on 1K of docs again
      6. Validate vbucket_seqno on each node

      Observation:

      Few vbuckets in node-3 has last_persisted_snap_start > last_persisted_seqno.

       vb_356:abs_high_seqno:             0
      		 
       vb_356:high_seqno:                 0
      		 
       vb_356:last_persisted_seqno:       0
      		 
       vb_356:last_persisted_snap_end:    1
      		 
       vb_356:last_persisted_snap_start:  1
      		 
       vb_356:purge_seqno:                0

      Test case used:

      From testrunner:
      		 
      failover.failovertests.FailoverTests.test_failover_stop_server,replicas=1,graceful=False,num_failed_nodes=1,load_ratio=10,flusher_batch_split_trigger=3,GROUP=P1

      Attachments

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

        Activity

          People

            ashwin.govindarajulu Ashwin Govindarajulu
            ashwin.govindarajulu Ashwin Govindarajulu
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty