From oak-issues-return-70328-archive-asf-public=cust-asf.ponee.io@jackrabbit.apache.org Tue Apr 9 14:56:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id B0336180763 for ; Tue, 9 Apr 2019 16:56:01 +0200 (CEST) Received: (qmail 80946 invoked by uid 500); 9 Apr 2019 14:36:23 -0000 Mailing-List: contact oak-issues-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: oak-dev@jackrabbit.apache.org Delivered-To: mailing list oak-issues@jackrabbit.apache.org Received: (qmail 80918 invoked by uid 99); 9 Apr 2019 14:36:23 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2019 14:36:23 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 6BB59E06F1 for ; Tue, 9 Apr 2019 14:56:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2914F2459A for ; Tue, 9 Apr 2019 14:56:00 +0000 (UTC) Date: Tue, 9 Apr 2019 14:56:00 +0000 (UTC) From: =?utf-8?Q?Michael_D=C3=BCrig_=28JIRA=29?= To: oak-issues@jackrabbit.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (OAK-7234) Check for outdated journal at startup MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/OAK-7234?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D168135= 07#comment-16813507 ]=20 Michael D=C3=BCrig commented on OAK-7234: ------------------------------------ Unassigning myself as there is no plans to take this up any time soon. > 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=C3=BCrig > Priority: Minor > Labels: resilience, tooling > > 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 c= ouple of concerns to address: > * What kind of tooling / guidance do we need to provide to recover shoul= d 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)? > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)