Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: 2.0
    • Component/s: XDCR
    • Security Level: Public
    • Labels:
      None

      Description

      • Place holder for adding error logging on the Source XDCR cluster.
      • Will add more as we come across more use-cases/scenarios.

      Replication failure due to the following reason should be logged - This will be helpful for support to troubleshoot errors and for any end-user.
      *Today most of the replication failures are debugged using ns_server logs, we should move the error displaying on the UI as well.

      Errors
      -----------------

      • Source replication cluster reference cannot be deleted if there is a replication is set up (another bug to track this - MB-6843)
      • Source replication is deleted - issue user-visible log message saying "Replication has been deleted" on source cluster
      • Source bucket is deleted - (1) Issue warning message to the user on delete bucket that replication is going on (2). issue user-visible log message saying "Bucket has been deleted, replication to remote bucket has stopped" on source cluster (3) Error message in the XDCR page on the replication impacted saying "Bucket has been delete, XDCR has stopped"
      • Source bucket is flushed - Cannot be done.

      For errors on the destination node and replication times out: raise this error on the source node .

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

        Activity

        ketaki Ketaki Gangal created issue -
        ketaki Ketaki Gangal made changes -
        Field Original Value New Value
        Priority Major [ 3 ] Critical [ 2 ]
        dipti Dipti Borkar made changes -
        Priority Critical [ 2 ] Blocker [ 1 ]
        dipti Dipti Borkar made changes -
        Description * Place holder for adding error logging on the Source XDCR cluster.
        - Will add more as we come across more use-cases/scenarios.

        Replication failure due to the following reason should be logged - This will be helpful for support to troubleshoot errors and for any end-user.
        *Today most of the replication failures are debugged using ns_server logs, we should move the error displaying on the UI as well.

        Errors
        -----------------
        - Delete Bucket on Destination , display error " Replication failed due to no-bucket to replicate on the destination"
        - Flush Bucket on Destination, display error " Replication failed due to flush executed on the destination"
        - Destination Cluster is down/unreachable - display error r " Replication failed, unable to reach destination"
        - Timeouts while trying to reach the destination cluster - This is most common and can occur under any/most conditions.
        Are there different levels of timeouts and can we classify errors based on these? It will be very useful when debugging the failures.

        - Source replication reference is deleted - Replication failed, missing replication reference?
        - Source replication is deleted - Replication failed, missing replication link
        - Source bucket is deleted - Replication failed, missing Source bucket
        - Source bucket is flushed - Error/Warning for Replication failed, Flush on source , Recreate replication
        - Source cluster is down/


        Warnings/ Error
        ------------------------
        - Replication attempt on mix cluster 1.8X and 2.0
        - Duplicate replication attempt between same bucket/cluster sets.
        - Warning if we see unusually higher[ some percentage] gets, higher conflicts on the destination - This would indicate something is wrong with the replication.

        * Place holder for adding error logging on the Source XDCR cluster.
        - Will add more as we come across more use-cases/scenarios.

        Replication failure due to the following reason should be logged - This will be helpful for support to troubleshoot errors and for any end-user.
        *Today most of the replication failures are debugged using ns_server logs, we should move the error displaying on the UI as well.

        Errors
        -----------------
        - Source replication cluster reference cannot be deleted if there is a replication is set up (another bug to track this - MB-6843)
        - Source replication is deleted - issue user-visible log message saying "Replication has been deleted" on source cluster
        - Source bucket is deleted - (1) Issue warning message to the user on delete bucket that replication is going on (2). issue user-visible log message saying "Bucket has been deleted, replication to remote bucket has stopped" on source cluster (3) Error message in the XDCR page on the replication impacted saying "Bucket has been delete, XDCR has stopped"
        - Source bucket is flushed - Cannot be done.


        For errors on the destination node and replication times out: raise this error on the source node .


        junyi Junyi Xie (Inactive) made changes -
        Assignee Junyi Xie [ junyi ] Aleksey Kondratenko [ alkondratenko ]
        alkondratenko Aleksey Kondratenko (Inactive) made changes -
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        farshid Farshid Ghods (Inactive) made changes -
        Status Resolved [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            alkondratenko Aleksey Kondratenko (Inactive)
            Reporter:
            ketaki Ketaki Gangal
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Gerrit Reviews

              There are no open Gerrit changes