# 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; [open/closed/suspended]. Required # 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. # Type: Type of job; [Bug/Feature]. Required. Job: SDP-180 Status: suspended Project: perforce-software-sdp Severity: C ReportedBy: tom_tyler ReportedDate: 2017/04/02 17:32:02 ModifiedBy: tom_tyler ModifiedDate: 2017/04/03 11:16:13 OwnedBy: tom_tyler Description: Solve 'big journal file' issue on replicas, maybe update sync_replica.sh. The problem is that the active journal file on a replica, the one named /p4/N/logs/journal, is not rotated automatically. DevNotes: This job, SDP-180, was originally named job000683. There is no plan to fix this, as it may be obsolete. It looks like using 'journalcopy' is the preferred method of updating a replica, and it doesn't have this problem, since it pulls directly numbered journal files in /p4/N/checkpoints. A workaround for replicas not using journalcopy is to just disable the journal file with '-J off'. It's not of much use anyway; without 'journalcopy' it's not a verbatim copy of the master journal, and so neither really trusted nor needed for recovery. It's value is mainly diagnostic for replication issues. Type: Feature