Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B9C27200B8B for ; Tue, 4 Oct 2016 12:18:33 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D4E11160AC9; Tue, 4 Oct 2016 10:18:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1E9DE160AC5 for ; Tue, 4 Oct 2016 12:18:24 +0200 (CEST) Received: (qmail 92809 invoked by uid 500); 4 Oct 2016 10:18:20 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 92799 invoked by uid 99); 4 Oct 2016 10:18:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Oct 2016 10:18:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 8E2632C044E for ; Tue, 4 Oct 2016 10:18:20 +0000 (UTC) Date: Tue, 4 Oct 2016 10:18:20 +0000 (UTC) From: "Emmanuel Lecharny (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DIRSERVER-2113) Integrate the 'partition-plumber' into ApacheDS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 04 Oct 2016 10:18:33 -0000 [ https://issues.apache.org/jira/browse/DIRSERVER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544987#comment-15544987 ] Emmanuel Lecharny commented on DIRSERVER-2113: ---------------------------------------------- Ok, the problem is that the SchemaManager is associated with the DirectoryService instance, which get created when we start the server. So the idea would be to start the server *without* starting the transport layer. That is somthing I can add to the existing code. > Integrate the 'partition-plumber' into ApacheDS > ----------------------------------------------- > > Key: DIRSERVER-2113 > URL: https://issues.apache.org/jira/browse/DIRSERVER-2113 > Project: Directory ApacheDS > Issue Type: New Feature > Affects Versions: 2.0.0-M20 > Reporter: Emmanuel Lecharny > Priority: Critical > Fix For: 2.0.0-M22 > > > Kiran has developped a small tool that fix a corrupted JDBM database : the {{partition-plumber}} (see https://svn.apache.org/repos/asf/directory/sandbox/kayyagari/partition-plumber/). > This is the only way we can get back on our feet when the database gets corrupted (if and only if the MasterTable is not itself corrupted, something that happens quite rarely). > I suggest strongly we inject this smart tool in the server so that a user with a corrupted database can repair it by starting the server with a special option (something like apacheds -repair). > That would save our users a lot of pain (like reloading the full database, assuming they have a recent backup...) -- This message was sent by Atlassian JIRA (v6.3.4#6332)