[
https://issues.apache.org/jira/browse/HBASE-3337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971156#action_12971156
]
stack commented on HBASE-3337:
------------------------------
Whats this? + public static final String HBCK_CODE_NAME = "HBCKsecret123";?
Its ugly. Can you make it uglier and more explanatory? Something like
'SERVER_NAME_USED_WHEN_HBCK_IS_DOING_MOVE'.
Your patch does not do the above suggested DISABLING?
> Restore HBCK fix of unassignment and dupe assignment for new master
> -------------------------------------------------------------------
>
> Key: HBASE-3337
> URL: https://issues.apache.org/jira/browse/HBASE-3337
> Project: HBase
> Issue Type: Bug
> Components: master, util
> Reporter: Jonathan Gray
> Assignee: Jonathan Gray
> Priority: Critical
> Fix For: 0.90.0, 0.92.0
>
> Attachments: HBASE-3337-v2.patch, HBASE-3337-v3.patch
>
>
> HBCK fixing of region unassignment and duplicate assignment was broken with
> the move to the new master.
> We've seen it happen doing testing of 0.90 RCs like that over in HBASE-3332.
> Rather than the old "clear everything out approach" which relied on the
> BaseScanner, in the new master we should just manipulate unassigned ZK nodes
> and let the master handle the transition.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
