Derby
  1. Derby
  2. DERBY-3501

Implement a JMX replicationMBean for monitoring of replication.

    Details

    • Type: Improvement Improvement
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 10.6.1.0
    • Fix Version/s: None
    • Component/s: JMX
    • Labels:
      None

      Description

      Imlement a replicationMBean for monitoring of replication. Example attributes

      • master/slave state
      • replication buffer usage
      • replication network traffic

        Issue Links

          Activity

          Hide
          Dyre Tjeldvoll added a comment -

          Removing Fix-version for unassigned issues

          Show
          Dyre Tjeldvoll added a comment - Removing Fix-version for unassigned issues
          Hide
          Francois Orsini added a comment -

          Please find Attached a first rev of Functional Spec for Derby Replication Monitoring via JMX.

          Comments are much appreciated.

          Show
          Francois Orsini added a comment - Please find Attached a first rev of Functional Spec for Derby Replication Monitoring via JMX. Comments are much appreciated.
          Hide
          Knut Anders Hatlen added a comment -

          Thanks for writing the functional spec, Francois. It looks good to me.

          One suggestion about the host/port attributes: On the master, we should call the attributes "SlaveHost" and "SlavePort" to make the names clearer. On the slave, I think we should repeat "SlaveHost" and "SlavePort" for completeness, and also change "HostName" to "MasterHost".

          The two links to the wiki don't work (they have a spurious # at the beginning).

          Show
          Knut Anders Hatlen added a comment - Thanks for writing the functional spec, Francois. It looks good to me. One suggestion about the host/port attributes: On the master, we should call the attributes "SlaveHost" and "SlavePort" to make the names clearer. On the slave, I think we should repeat "SlaveHost" and "SlavePort" for completeness, and also change "HostName" to "MasterHost". The two links to the wiki don't work (they have a spurious # at the beginning).
          Hide
          Rick Hillegas added a comment -

          Thanks for the great spec, Francois. I have some comments:

          o It would be nice to have TOC entries for the following sections: Assumptions, Requirements, Replication MBean, and Attributes.

          o There's a Javadoc entry in the TOC but no corresponding section further down.

          o I would recommend changing the names of some of the attributes:

          • Master attributes:

          HostName -> SlaveHostName
          PortNumber -> SlavePortNumber
          LastInstant -> LastLogInstant
          LastShipped -> LastLogChunkShipped

          • Slave attributes:

          HostName -> MasterHostName
          LastInstant -> LastLogInstant
          LastReceived -> LastLogChunkReceived

          o In "JMX Client API and ReplicationMBean Access", did you intend for the last line of the first code block to appear in a bigger font and to be split off from the previous line?

          o Could you give us an example of how to use the ping feature?

          o I agree that writing a VisualVM plugin for Derby would be very useful. You may have some idea of how hard that is-I don't! I don't know what the licensing issues are for such a plugin so I can't say whether this work is even possible for our Apache community. Provided that there are no intractable licensing issues, I think that this work falls inside the Derby charter-but other community members may have other opinions.

          o Public API - The existing MBeans are documented in our public api in the org.apache.derby.mbeans package. I think that we should document this new MBean there too.

          Show
          Rick Hillegas added a comment - Thanks for the great spec, Francois. I have some comments: o It would be nice to have TOC entries for the following sections: Assumptions, Requirements, Replication MBean, and Attributes. o There's a Javadoc entry in the TOC but no corresponding section further down. o I would recommend changing the names of some of the attributes: Master attributes: HostName -> SlaveHostName PortNumber -> SlavePortNumber LastInstant -> LastLogInstant LastShipped -> LastLogChunkShipped Slave attributes: HostName -> MasterHostName LastInstant -> LastLogInstant LastReceived -> LastLogChunkReceived o In "JMX Client API and ReplicationMBean Access", did you intend for the last line of the first code block to appear in a bigger font and to be split off from the previous line? o Could you give us an example of how to use the ping feature? o I agree that writing a VisualVM plugin for Derby would be very useful. You may have some idea of how hard that is- I don't! I don't know what the licensing issues are for such a plugin so I can't say whether this work is even possible for our Apache community. Provided that there are no intractable licensing issues, I think that this work falls inside the Derby charter -but other community members may have other opinions. o Public API - The existing MBeans are documented in our public api in the org.apache.derby.mbeans package. I think that we should document this new MBean there too.
          Hide
          Francois Orsini added a comment -

          Knut, Rick, Thanks for the great comments.

          I'm incorporating them and will post a new rev. Cheers.

          Show
          Francois Orsini added a comment - Knut, Rick, Thanks for the great comments. I'm incorporating them and will post a new rev. Cheers.
          Hide
          Jørgen Løland added a comment -

          Thanks for the spec, Francois.

          In addition to the comments made by Knut and Rick, I think it would be interesting to know the latency of log shipping, something like:

          "Log instant X was sent to the slave 713ms after it was written to disk on the master"

          Show
          Jørgen Løland added a comment - Thanks for the spec, Francois. In addition to the comments made by Knut and Rick, I think it would be interesting to know the latency of log shipping, something like: "Log instant X was sent to the slave 713ms after it was written to disk on the master"
          Hide
          Kristian Waagan added a comment -

          Unassigned due to inactivity.

          Show
          Kristian Waagan added a comment - Unassigned due to inactivity.

            People

            • Assignee:
              Unassigned
              Reporter:
              Bernt M. Johnsen
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:

                Development