[
https://issues.apache.org/jira/browse/HBASE-22855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908276#comment-16908276
]
Andrew Purtell commented on HBASE-22855:
----------------------------------------
I implemented HBASE-21464 as a workaround. Due to time constraints I didn't
find a root cause in the time I had to look into the issue and I felt rewriting
what I wanted to rewrite would have been more risky. Likely the result would
not be appropriate for a patch release too. We can certainly revert that change
and attempt to fix (by rewrite, in my opinion) whatever issue exists in the
recursive locateRegion and relocateRegion method chains. Or maybe it is a more
complex set of events and cross process timing as in the above hypothetical
scenario.
> 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)
