You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2010/10/29 23:28:20 UTC

[jira] Commented: (HBASE-3172) Reverse order of AssignmentManager and MetaNodeTracker in ZooKeeperWatcher

    [ https://issues.apache.org/jira/browse/HBASE-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12926463#action_12926463 ] 

stack commented on HBASE-3172:
------------------------------

+1

> Reverse order of AssignmentManager and MetaNodeTracker in ZooKeeperWatcher
> --------------------------------------------------------------------------
>
>                 Key: HBASE-3172
>                 URL: https://issues.apache.org/jira/browse/HBASE-3172
>             Project: HBase
>          Issue Type: Bug
>          Components: master, zookeeper
>    Affects Versions: 0.90.0
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.90.0
>
>         Attachments: HBASE-3172-v1.patch
>
>
> Over in HBASE-3159, I reported a similar double-opened issue but for META.  This is because of the fact that the META unassigned znode has two different consumers {{MetaNodeTracker}} in use by the CatalogTracker and {{AssignmentManager}} which uses it for normal regions-in-transition stuff.
> The AssignmentManager needs to go first, otherwise we can get double handling of state transitions.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.