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

          No work has yet been logged on this issue.

            People

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

              Dates

              • Created:
                Updated:

                Development