[
https://issues.apache.org/jira/browse/BOOKKEEPER-738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910103#comment-13910103
]
Rakesh R commented on BOOKKEEPER-738:
-------------------------------------
Hi Ivan, I've attached initial patch based on the following thoughts/idea in my
mind and yet to write test cases for the same.
Please have a look at the attached patch. Thanks.
Defined one parent bean for the autorecovery and which will be holding the
child beans as shown below:
AutoRecoveryMXBean :-
- LedgerUrMXBean
- AuditorParticipantMXBean
- ReplicationWorkerMXBean
Autorecovery will be in two form and I feel we could build relationship based
on that, like:
# Daemon : Here the idea is to register AutoRecoveryMXBean under the
BookieServerMXBean and so on.
# Standalone : Here the idea is to define 'org.apache.AutoRecoveryService' and
register all the autorecovery beans under this. I've kept snapshot of this in
the umbrella JIRA BOOKKEEPER-736.
> Provide jmx bean registration mechanism
> ---------------------------------------
>
> Key: BOOKKEEPER-738
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-738
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: bookkeeper-auto-recovery
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 4.3.0
>
> Attachments: 0001-BOOKKEEPER-738-AutoRecovery-Registry.patch
>
>
> This JIRA to discuss the way to do the registration of the exposed beans in
> the autorecovery module.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
