db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Burlison (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3927) programmatic access to replication status
Date Thu, 06 Aug 2009 12:46:15 GMT

    [ 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:
>         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.

View raw message