[
https://issues.apache.org/jira/browse/HBASE-8144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610923#comment-13610923
]
Jimmy Xiang commented on HBASE-8144:
------------------------------------
[[email protected]], good catch, will fix.
[~ram_krish], we don't need other synchronization on failedOpenTracker since is
it is concurrent hash map, and the block is already synchronized on region
name. I can add a warning message to the log in case a region is transitioned
to failed_open/close. As to the reason why it failed, we can check the region
server log. It is a good idea to put in the znode and pass back to the master.
From the master web UI, the user can see the region is failed to open/close so
s/he can start to check out the log. It is also a good idea to put such
information in region states and show on master web UI directly. We can work on
this in a different patch.
As to reassign those regions failed to open/close, currently, we have to use
hbase shell. It must be triggered by the client, since TOM is going to gone.
> Limit number of attempts to assign a region
> -------------------------------------------
>
> Key: HBASE-8144
> URL: https://issues.apache.org/jira/browse/HBASE-8144
> Project: HBase
> Issue Type: Bug
> Components: Region Assignment
> Reporter: Jimmy Xiang
> Assignee: Jimmy Xiang
> Priority: Minor
> Fix For: 0.95.0, 0.98.0
>
> Attachments: trunk-8144.patch
>
>
> In sending a region open request to a region server, we make sure we try at
> most some configured times. However, once the request is accepted by the
> region server, the region could go through this transition forever:
> failed_open (in ZK) => closed => opening => failed_open (in ZK), assuming no
> RPC/network issue.
> It will be good to break the loop and limit the number of tries and move the
> region to failed_open state (will be introduced in HBASE-8137)
--
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
