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

[Correctness] Write a test plan to assert that PiTR is functionally viable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • Morpheus
    • Morpheus
    • tools
    • None

    Description

      What's the issue?
      We've tested our PiTR feature as a prototype, and we understand how it works/how it solves the problem, however, we should think up some edge cases/use cases and validate that our solution will resolve these types of problems.

      As an example, we'd like to know:

      1) Does it work after a failover?
      2) Is PiTR related information maintained for replicas?
      3) When an replica is promoted to an active, have we lost PiTR information?
      4) What about XDCR, are we OK to lose PiTR information in this case?

      What's the fix?
      Write up a small test plan, which contains example scenarios which will stress PiTR in such a way that we can determine if the design is valid.

      Attachments

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

        Activity

          People

            Matt.Hall Matt Hall
            james.lee James Lee
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty