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

KV should use the Chronicle history ID provided in collections manifest to "force" manifests on vbuckets

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.0.0
    • Cheshire-Cat
    • couchbase-bucket
    • None
    • Untriaged
    • 1
    • Unknown
    • KV-Engine 2021-March, KV-Engine CC Final Sprint

    Description

      So that after an unsafe failover, vbucket manifests are correctly squared with the system manifest. "Forcing" a manifest on a vbucket means that collections in the new manifest should be compared with collections in the old manifest by collection ID, name and containing scope ID and any collections which don't exist in the new manifest by do in the old should be deleted, in addition to any collections which exists in the new but not in the old should be created.

      Attachments

        Issue Links

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

          Activity

            People

              jwalker Jim Walker
              dfinlay Dave Finlay
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                PagerDuty