Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1636696501.1249562775081.JavaMail.jira@brutus>
Date: Thu, 6 Aug 2009 05:46:15 -0700 (PDT)
From: "Alan Burlison (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-3927) programmatic access to replication
 status
In-Reply-To: <1219509883.1225277864753.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740031#action_12740031 ] 

Alan Burlison commented on DERBY-3927:
--------------------------------------

We would like to monitor this from Nagios, so stored procedures might be easier, or a sys table with the info in it, perhaps?

> programmatic access to replication status
> -----------------------------------------
>
>                 Key: DERBY-3927
>                 URL: https://issues.apache.org/jira/browse/DERBY-3927
>             Project: Derby
>          Issue Type: Improvement
>          Components: Replication
>    Affects Versions: 10.4.2.0
>         Environment: N/A
>            Reporter: Andrew Lawrenson
>            Priority: Minor
>
> It would be very useful to be able to get programmatic information on the current state of derby replication, from either the master or server nodes.
> this could be either via stored procedures, or JMX (my preference)
> this could be used, for example, to check if a master has exceeded its log buffer after being disconnected from the slave.  Or to check if the slave is still connected to the master.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.