SDP-895
Open
Enhance the p4d start up procedure to better handle the scenario where corruption is detected in the journal file.
The SDP can detect the corruption but all it does is rotate the journal. This leaves p4d functional but it leaves the offline database in a bad state. The next nightly offline checkpoint will fail when attempting to replay the latest journal files to the offline database.
I think the SDP should do one of the following:
1) The most ideal situation is if the SDP can detect the corruption to first rotate the journal but then also run live_checkppint. This will get the offline database in a good state so that the next nightly offline checkpoint will succeed.
2) if there is no way to accomplish option #1 I think the SDP should have a configurable (opt in / opt out) to exit when corruption is detected in the journal file.
The SDP can detect the corruption but all it does is rotate the journal. This leaves p4d functional but it leaves the offline database in a bad state. The next nightly offline checkpoint will fail when attempting to replay the latest journal files to the offline database.
I think the SDP should do one of the following:
1) The most ideal situation is if the SDP can detect the corruption to first rotate the journal but then also run live_checkppint. This will get the offline database in a good state so that the next nightly offline checkpoint will succeed.
2) if there is no way to accomplish option #1 I think the SDP should have a configurable (opt in / opt out) to exit when corruption is detected in the journal file.
- Status
- Open
- Project
- perforce-software-sdp
- Severity
- C
- Reported By
- Andy Boutte
- Reported Date
- 2 years ago
- Modified By
- C. Thomas Tyler
- Modified Date
- 2 years ago
- Owned By
- andy_boutte
- Component
- core-unix
- Type
- Feature
Log in to comment