[
https://issues.apache.org/jira/browse/BOOKKEEPER-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925194#comment-13925194
]
Rakesh R commented on BOOKKEEPER-736:
-------------------------------------
[~hustlmsp] [~i0exception] Could you please give some insight on few things:
- I failed to see any testcases to know the usage pattern.
- My usecase is to link JMX beans to the existing monitoring tool - How does
the 'opStatsLogger' interact with JMX. I've got confused by seeing the
following deprecation comments.
{code}
/**
* @return Returns an OpStatsData object with necessary values. We need
this function
* to support JMX exports. This should be deprecated sometime in the near
future.
* populated.
*/
public OpStatsData toOpStatsData();
{code}
- I could see OpStatsData is the entity used by OpStatsLogger, but I think it
is well designed for the latency attributes. Is there any plan to extend this
to support more attributes. I've added the metrics which autorecovery module is
interested, please see it once.
[AutoRecovery feature interested
metrics|https://issues.apache.org/jira/browse/BOOKKEEPER-737?focusedCommentId=13910091&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13910091]
> JMX support for AutoRecovery
> ----------------------------
>
> Key: BOOKKEEPER-736
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-736
> Project: Bookkeeper
> Issue Type: New Feature
> Components: bookkeeper-auto-recovery
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments:
> Prototype-JMX-beans-for-standalone-autorecovery-process.png
>
>
> Idea of this JIRA is to provide jmx interfaces to get the statistics of the
> auto recovery activities.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
