Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-567 Better support for replication on multi-homed servers
  3. OPENDJ-4443

Developer task: Use per-process UUID to uniquely identify a server instance

    Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 6.0.0
    • Fix Version/s: 6.5.0
    • Component/s: devops, replication
    • Labels:
      None
    • Sprint:
      Sprint 5, Sprint 6, Sprint 7, Sprint 8, Sprint 9, Sustaining Sprint 1, Sustaining Sprint 2, Sustaining Sprint 3, OpenDJ Sprint 127
    • Story Points:
      7

      Description

      To make sure a server is uniquely identified, use a per-process UUID to identify a server instance. The UUID is not meant to be persisted, it will be re-generated each time the server starts.

      This UUID will be used mainly for two purposes:

      • computation of the best RS for a DS : use the same UUID as first choice (in the case of a DSRS)
      • to avoid the DUPLICATE_SERVER_ID error when the server is not correctly identified as itself in a multihoming case.

      The UUID must be sent in replication protocol messages (in the replication handshake phase). Need for a new replication protocol version.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ylecaillez Yannick Lecaillez
                Reporter:
                nicolas.capponi@forgerock.com Nicolas Capponi
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: