# The form data below was edited by tom_tyler # Perforce Workshop Jobs # # Job: The job name. 'new' generates a sequenced job number. # # Status: Job status; required field. There is no enforced or # promoted workflow for transition of jobs from one # status to another, just a set of job status values # for users to apply as they see fit. Possible values: # # open - Issue is available to be worked on. # # inprogress - Active development is in progress. # # blocked - Issue cannot be implemented for some reason. # # fixed - Fixed, optional status to use before closed. # # closed - Issue has been dealt with definitively. # # punted - Decision made not to address the issue, # possibly not ever. # # suspended - Decision made not to address the issue # in the immediate future, but noting that it may # have some merit and may be revisited later. # # duplicate - Duplicate of another issue that. # # obsolete - The need behind the request has become # overcome by events. # # Project: The project this job is for. Required. # # Severity: [A/B/C] (A is highest) Required. # # ReportedBy The user who created the job. Can be changed. # # ReportedDate: The date the job was created. Automatic. # # ModifiedBy: The user who last modified this job. Automatic. # # ModifiedDate: The date this job was last modified. Automatic. # # OwnedBy: The owner, responsible for doing the job. Optional. # # Description: Description of the job. Required. # # DevNotes: Developer's comments. Optional. Can be used to # explain a status, e.g. for blocked, punted, # obsolete or duplicate jobs. May also provide # additional information such as the earliest release # in which a bug is known to exist. # # Component: Projects may use this optional field to indicate # which component of the project a givenjob is associated # with. # # For the SDP, the list of components is defined in: # //guest/perforce_software/sdp/tools/components.txt # # Type: Type of job [Bug/Feature/Problem]. Required. # Feature and Bug are common terms. # A Problem is suspected bug, or one without a clear # understanding of exactly what is broken. # # Release: Release in which job is intended to be fixed. Job: SDP-204 Status: closed Project: perforce-software-sdp Severity: B ReportedBy: tom_tyler ReportedDate: 2017/04/05 10:58:46 ModifiedBy: tom_tyler ModifiedDate: 2022/05/13 18:32:45 OwnedBy: tom_tyler Description: Support HMS automated failover of 'standby' journalcopy replica. HMS supports failover of a forwarding replica, but not a forwarding 'standby' replica that uses journalcopy. The mkrep.sh script knows the details of creating a 'standby' replica, i.e. one that uses the journalcopy command in a startup.N thread, and pulls a byte-for-byte verbatim journal file from the master server into a pre-rotated journal file (honoring journalPrefix for the target path). The details of manually failing over a standby replica differ slightly from a old-style forwarding replica, and are well captured in the SDP Guide. The 'hms failover' automation needs to detect whether a replica is a journalcopy replica or not, and must account for the slightly different procedures for failing over to a standby replica. We expect 'journalcopy' replicas to become more common, so as time goes by, the priority on this increases. DevNotes: This become HMS-8. Component: hms Type: Feature