# 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. # # 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]. Required. Job: SDP-214 Status: suspended Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2017/04/20 21:07:29 ModifiedBy: tom_tyler ModifiedDate: 2018/10/25 07:31:03 OwnedBy: tom_tyler Description: HMS failover should reset state file on non-standby replicas after failover of master. With replicas of type other than '*standby', a failover of the master server will 'break' replication on downstream replicas. This requires the replication 'state' files on each replica/edge server to be reset, and the replica 'p4d' processes bounced, following a failover of the master. HMS could implement this logic. DevNotes: 2018-10-25 tom_tyler: I am suspending this job because the modern best practice is to ONLY use 'standby' type relicas for failover, and to achieve the failover only with 'p4 failover' command, which fully handles impact on on downstream replicas of a failover of the master. Component: hms Type: Bug