Derby
  1. Derby
  2. DERBY-3927

programmatic access to replication status

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 10.4.2.0
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Environment:
      N/A

      Description

      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.

        Issue Links

          Activity

          Hide
          Alan Burlison added a comment -

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

          Show
          Alan Burlison added a comment - We would like to monitor this from Nagios, so stored procedures might be easier, or a sys table with the info in it, perhaps?
          Hide
          Bernt M. Johnsen added a comment -

          Possibly a duplicate?

          Show
          Bernt M. Johnsen added a comment - Possibly a duplicate?
          Hide
          Dag H. Wanvik added a comment -

          DERBY-3501 speaks only of a JMX-based solution. This issue has a more open requirement: for any API.
          If we decide to go for JMX, we should close one of these as a dup, I agree.

          Show
          Dag H. Wanvik added a comment - DERBY-3501 speaks only of a JMX-based solution. This issue has a more open requirement: for any API. If we decide to go for JMX, we should close one of these as a dup, I agree.
          Hide
          Francois Orsini added a comment -

          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.

          Show
          Francois Orsini added a comment - 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.

            People

            • Assignee:
              Unassigned
              Reporter:
              Andrew Lawrenson
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:

                Development