Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-1053

Improve logging of replication load balancing and fail-over in order to diagnose the causes of these events

    XMLWordPrintable

Details

    • Improvement
    • Status: Done
    • Major
    • Resolution: Fixed
    • 2.6.0
    • 2.6.1, 2.8.0, 3.0.0
    • replication
    • None

    Description

      As an administrator I would like to be able to answer questions like, "why did DS X switch from RS A to RS B?".

      We could log more detailed information when a replica (DS) switches from one replication server (RS) to another. However, this can sometimes lead to very noisy replication logs in cases where the network is misbehaving. In addition, users may have switched of logging of this type of event. Instead of or as well as logging, we could publish two pieces of information to the replication monitor: 1) the most recent reason why the DS disconnected from an RS, 2) why the DS is connected to the current RS (e.g. same JVM, same host, same group, etc).

      Attachments

        Activity

          People

            JnRouvignac Jean-Noël Rouvignac
            matthew Matthew Swift
            Jean-Noël Rouvignac Jean-Noël Rouvignac
            Christophe Sovant Christophe Sovant
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: