accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1586) If initial port binding fails, ThriftMetrics MBean is never registered for subsequently bound TServer
Date Mon, 22 Jul 2013 18:26:49 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13715491#comment-13715491
] 

ASF subversion and git services commented on ACCUMULO-1586:
-----------------------------------------------------------

Commit 1a48f7c34da98f4ba1fe3fac133081ee5f35caca in branch refs/heads/master from [~ecn]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=1a48f7c ]

ACCUMULO-1586 committing Michael Berman's patch

                
> If initial port binding fails, ThriftMetrics MBean is never registered for subsequently
bound TServer
> -----------------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-1586
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1586
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.0
>            Reporter: Michael Berman
>            Assignee: Michael Berman
>             Fix For: 1.5.1, 1.6.0
>
>         Attachments: ACCUMULO-1586.patch
>
>
> When trying a range of ports, the MBean for reporting metrics is registered before the
connection has had an opportunity to fail.  If it fails and we try a new port, the same MBean
objectName is used for registering the new ThriftMetrics object created for the new server.
 This fails because there is already an MBean registered with that name.  A couple possible
fixes: wait to register until we're sure the connection has succeeded; create the timed processor
outside the port-binding loop; or deregister the bean after a failure.

--
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

Mime
View raw message