[
https://issues.apache.org/jira/browse/HBASE-22855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908073#comment-16908073
]
jianghua zhu commented on HBASE-22855:
--------------------------------------
There is one possibility:
Assuming that HMaster, HRegionServer1, and HRegionServer2 exist, the following
processes occur.
1.HMaster sends a request to HRegionServer1 via RPC via the assign mechanism to
load the Region information corresponding to hbase:meta.
2. The HRegionServer itself, for some reason, failed to report state to
HMaster, and HMaster assumed that the HRegionServer was dead.
3.HMaster makes a request to HRegionServer2 via the assign mechanism to load
the Region information corresponding to hbase:meta. And the HRegionServer2
loads quickly.
4. Retrieve the location of the hbase:meta at HRegionServer2
> Find the root cause why still using the old hbase:meta location after meta
> region moving.
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-22855
> URL: https://issues.apache.org/jira/browse/HBASE-22855
> Project: HBase
> Issue Type: Bug
> Reporter: Zheng Hu
> Assignee: Zheng Hu
> Priority: Major
>
> In HBASE-214644, [[email protected]] had a nice fix about the using
> the stale hbase:meta location, say update the hbase:meta location
> periodically. Also someone in user list also encountered this bug in
> HBASE1.4.9 [1].
> [~wenbang] from DiDi also have a question about the root cause under
> HBASE-214644 [2].
> I think we need to find out the root cause and fix it ?
> [1].
> https://mail-archives.apache.org/mod_mbox/hbase-user/201908.mbox/%3C114F31E6-B7F9-4209-AAE3-32A022729593%40gmail.com%3E
> [2].
> https://issues.apache.org/jira/browse/HBASE-21464?focusedCommentId=16902808&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16902808
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
