directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRSERVER-2113) Integrate the 'partition-plumber' into ApacheDS
Date Tue, 04 Oct 2016 07:46:20 GMT

    [ https://issues.apache.org/jira/browse/DIRSERVER-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544648#comment-15544648
] 

Emmanuel Lecharny commented on DIRSERVER-2113:
----------------------------------------------

Ah, crap... 

I will have a look at why the start is necessary (which should not be...).

Regarding the sysout vs log, it may be because I looked at teh 'Value' branch, not trunk.

I'll get both issue fixed. Thanks for having added the action in Studio !

> 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)

Mime
View raw message