Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Date: Wed, 20 Feb 2013 11:25:12 +0000 (UTC)
From: "Unico Hommes (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Message-ID: <JIRA.12633173.1361359448507.309947.1361359512691@arcas>
In-Reply-To: <JIRA.12633173.1361359448507@arcas>
References: <JIRA.12633173.1361359448507@arcas>
Subject: [jira] [Created] (JCR-3525) Enable consistency checker to run in
 fix mode in a live cluster
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Unico Hommes created JCR-3525:
---------------------------------

             Summary: Enable consistency checker to run in fix mode in a live cluster
                 Key: JCR-3525
                 URL: https://issues.apache.org/jira/browse/JCR-3525
             Project: Jackrabbit Content Repository
          Issue Type: Improvement
          Components: clustering, jackrabbit-core
            Reporter: Unico Hommes
            Assignee: Unico Hommes


When the database consistency checker repairs inconsistent bundles it operates directly on the underlying persistence manager. But this method bypasses the cluster update mechanism that is built into the shared item state manager. This makes it impossible to run the consistency checker in a live cluster. It is possible for the consistency checker to notify the cluster of the changes it makes during repairs by providing it with an update event channel.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira