You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2013/01/24 18:19:13 UTC

[jira] [Updated] (BOOKKEEPER-556) BookieServerMXBean#getServerState makes no sense

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivan Kelly updated BOOKKEEPER-556:
----------------------------------

    Attachment: 0001-BOOKKEEPER-556-BookieServerMXBean-getServerState-mak.patch

Removed getServerState and more unused junk from the class.
                
> BookieServerMXBean#getServerState makes no sense
> ------------------------------------------------
>
>                 Key: BOOKKEEPER-556
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-556
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>             Fix For: 4.3.0
>
>         Attachments: 0001-BOOKKEEPER-556-BookieServerMXBean-getServerState-mak.patch
>
>
> This got carried over from zookeeper during a copy paste. In ZooKeeper it's used to specify whether a server is standalone or not. This isn't relevant for BookKeeper.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira