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

[BucketDurability]: Updated bucket durability level is not taken into effect immediately

    XMLWordPrintable

Details

    • Untriaged
    • Centos 64-bit
    • 1
    • Unknown

    Description

      Build: 6.6.0-7724

      Steps to reproduce:

      1. Two node cluster, Couchbase bucket(replicas=2, bucket_durability_level=None)
      2. Update bucket durability using REST API
      3. Immediately try a async_write from Java SDK client (Assuming the async_write will be promoted to sync_write internally)

      Observation:

      The attempted indirect sync_write was taken as async_write only.

      ]# /opt/couchbase/bin/cbstats -u Administrator -p password localhost:11210 vbucket-details 342 | grep committed
       vb_342:sync_write_committed_count: 0

      Attempting a async_write after some time (say 10seconds) is resulting in incrementing the sync_write counter.

      Server logs:

      https://cb-jira.s3.us-east-2.amazonaws.com/logs/b_durability_sync_write_counter/collectinfo-2020-06-01T191826-ns_1%4010.112.191.101.zip
      https://cb-jira.s3.us-east-2.amazonaws.com/logs/b_durability_sync_write_counter/collectinfo-2020-06-01T191826-ns_1%4010.112.191.102.zip

      Attaching pcap bucket_d_update_with_client_error.pcapng for further debugging.

      Attachments

        Issue Links

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

          Activity

            dfinlay Dave Finlay added a comment -

            This is desirable but actually not required and was discussed in the requirements doc: https://docs.google.com/document/d/1rB1WZizZU8uKt49ET6ZmUB55LqsAWDxxtZ-XSa8MlxE/edit?disco=AAAAJIKXNSM. It's difficult to implement and we didn't do it - so I imagine this ticket should be resolved as incomplete.

            CC: Shivani Gupta

            dfinlay Dave Finlay added a comment - This is desirable but actually not required and was discussed in the requirements doc: https://docs.google.com/document/d/1rB1WZizZU8uKt49ET6ZmUB55LqsAWDxxtZ-XSa8MlxE/edit?disco=AAAAJIKXNSM . It's difficult to implement and we didn't do it - so I imagine this ticket should be resolved as incomplete. CC: Shivani Gupta

            Agree with Dave's comment - this is not required behavior. We will document that there can be a delay between changing the bucket durability setting and actually have new writes confirm to that setting.

            shivani.gupta Shivani Gupta added a comment - Agree with Dave's comment - this is not required behavior. We will document that there can be a delay between changing the bucket durability setting and actually have new writes confirm to that setting.
            owend Daniel Owen added a comment -

            Created DOC-6883 to ensure we document in the section on bucket level durability.
            As suggested, resolving the ticket as incomplete.

            owend Daniel Owen added a comment - Created DOC-6883 to ensure we document in the section on bucket level durability. As suggested, resolving the ticket as incomplete.

            People

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

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty