[
https://issues.apache.org/jira/browse/HBASE-5677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251880#comment-13251880
]
Lars Hofhansl commented on HBASE-5677:
--------------------------------------
@xufeng: OK, thanks. This is caused by the client?
Back to my previous comment. I think a good definition for declaring the master
"running" is when it is fully initialized. I'd still just add this extra check
to isMasterRunning. Is anything failing with that? If so I'd like to understand
why?
BTW. This is the only issue holding up the next RC for the first 0.94 release.
> The master never does balance because duplicate openhandled the one region
> --------------------------------------------------------------------------
>
> Key: HBASE-5677
> URL: https://issues.apache.org/jira/browse/HBASE-5677
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.90.6
> Environment: 0.90
> Reporter: xufeng
> Assignee: xufeng
> Fix For: 0.90.7, 0.92.2, 0.94.0, 0.96.0
>
> Attachments: HBASE-5677-90-v1.patch,
> surefire-report_no_patched_v1.html, surefire-report_patched_v1.html
>
>
> If region be assigned When the master is doing initialization(before do
> processFailover),the region will be duplicate openhandled.
> because the unassigned node in zookeeper will be handled again in
> AssignmentManager#processFailover()
> it cause the region in RIT,thus the master never does balance.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
