[
https://issues.apache.org/jira/browse/DERBY-3927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12740349#action_12740349
]
Francois Orsini commented on DERBY-3927:
----------------------------------------
We could also have a top level enhancement JIRA for Derby replication
Monitoring in general and have these 2 JIRAs being sub-ones as different
sub-tasks if having both approaches makes sense.
> 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.
