Michael Dürig created OAK-7234: ---------------------------------- Summary: Check for outdated journal at startup Key: OAK-7234 URL: https://issues.apache.org/jira/browse/OAK-7234 Project: Jackrabbit Oak Issue Type: Improvement Components: segment-tar Reporter: Michael Dürig
To prevent accidentally branching the repository when the {{journal.log}} became outdated (e.g. OAK-3702) we could add an additional safety feature which would prevent the repository from starting in such cases. There's a couple of concerns to address: * What kind of tooling / guidance do we need to provide to recover should such a situation be detected? * How do we detect the {{journal.log}} being outdated? * How do we prevent false positives? * How do we deal with situation where the {{journal.log}} modifications are intended (e.g. by tools, of manual interventions)? -- This message was sent by Atlassian JIRA (v7.6.3#76005)