Details

    • Type: New Feature
    • Status: Closed
    • Priority: Medium
    • Resolution: Fixed
    • Affects versions: None
    • Fix versions: 12.0.1, 10.2.1-patch5
    • Labels:
      None
    • Platform:
      All
    • SalesForce Case ID:
      10516, 11883
    • Acceptance Test:
      Hide
      ReplicationMetricWithBackupAndMirrorDownTest none none
      ReplicationMetricWithBackupTest none none
      Show
      ReplicationMetricWithBackupAndMirrorDownTest none none ReplicationMetricWithBackupTest none none
    • Sprint:
    • Product:
      XAP
    • Edition:
      Open Source

      Description

      Reproduction:
      1. config metrics
      2. start the grid with one primary and one backup
      3. deploy space with EDS (attached module that you can use).
      4. do not deploy mirror.
      5. start benchmark.
      6. as the mirror is down, you will see the redolog raising in the ui
      7. in your metric reporter you will see that the value of space_replication_redo-log_size is also raising (this is the primary redolog saved for the mirror)
      8. restart the primary.

      Expected:
      the backup become primary and his space_replication_redo-log_size metric will keep raising.

      Actual result:
      from this point the primary that become backup and got a new pid starts report on space_replication_redo-log_size = 0 and the backup that become primary doesn't report at all on this metric.

      Seems that we need to do new registration "after primary"
        

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: