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

XDCR should not auto-delete replications if the target bucket is deleted

    XMLWordPrintable

Details

    • Task
    • Resolution: Unresolved
    • Major
    • Morpheus
    • 4.0.0, 5.0.0
    • XDCR
    • None

    Description

      If the target bucket for a replication is deleted, we quietly drop that replication and log the following:

      Replication from bucket "beer-sample" to bucket "Empty" on cluster "Receiver" removed, since the target bucket "Empty" has been deleted
      

      Although I can see scenarios where we wouldn't care about knowing this, I can also see a lot of scenarios where I would like to know about it. If someone has just nuked my DR bucket, I want to know about that ASAP on my prod cluster. Unless I'm parsing our logging (difficult) or manually reading the logs tab (unlikely), the only way I can see this from my prod cluster is to notice the absence of the replication in the XDCR tab (which might not be something I look at too often). Even then, if I have a few buckets replicating to a few clusters, the list in the XDCR tab is going to be pretty long - I'm not going to immediately notice one is missing.

      Personally, I think the best answer would be to show the replication in red (or otherwise highlighted) in the list, and perhaps a warning popup too.

      Attachments

        Issue Links

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

          Activity

            People

              neil.huang Neil Huang
              James Flather James Flather (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty