SDP-439
Closed
DOC: SDP Guide for setting up a replica is missing key items.
The SDP Guide provides a few basic steps for creating "a simple readonly replica", but is missing some standard/best-practice requirements. Specifically:
It does not mention the best-practice approach of creating a server spec for each of the master and replica server instances;
It does not state the need to set P4TICKETS for the replica, required to ensure the service user ticket is available to the replica server (recommended in the P4DIST guide);
It does not include 'journalPrefix' for the replica instance (recommended in the P4DIST guide);
It does not include the setting of P4JOURNAL (requiring a 'p4d -cset' command);
It does not include the best-practice of setting P4LOG (recommended in the P4DIST guide);
It does not include the use of 'server.depot.root'.
For an SSL-enabled server, P4TRUST should also be set, and the corresponding 'p4 trust' command run on the replica server.
These are used or relied upon by various of the SDP scripts and processes; some will fail if not set correctly, and some will prevent the replica from starting in the first place.
The SDP Guide provides a few basic steps for creating "a simple readonly replica", but is missing some standard/best-practice requirements. Specifically:
It does not mention the best-practice approach of creating a server spec for each of the master and replica server instances;
It does not state the need to set P4TICKETS for the replica, required to ensure the service user ticket is available to the replica server (recommended in the P4DIST guide);
It does not include 'journalPrefix' for the replica instance (recommended in the P4DIST guide);
It does not include the setting of P4JOURNAL (requiring a 'p4d -cset' command);
It does not include the best-practice of setting P4LOG (recommended in the P4DIST guide);
It does not include the use of 'server.depot.root'.
For an SSL-enabled server, P4TRUST should also be set, and the corresponding 'p4 trust' command run on the replica server.
These are used or relied upon by various of the SDP scripts and processes; some will fail if not set correctly, and some will prevent the replica from starting in the first place.
- Status
- Closed
- Project
- perforce-software-sdp
- Severity
- A
- Reported By
- Adam Morriss
- Reported Date
- Modified By
- Robert Cowham
- Modified Date
- Owned By
- amo
- Dev Notes
- This has been fixed for now with the documentation of mkrep.sh which is recommended way to do things.
- Component
- doc
- Type
- Bug