[
https://issues.apache.org/jira/browse/HBASE-14453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14876551#comment-14876551
]
Andrew Purtell edited comment on HBASE-14453 at 9/18/15 10:10 PM:
------------------------------------------------------------------
HBaseAdmin#deleteTable, when determining if table regions are still in the
catalog, would contact the regionserver hosting meta directly for scanning in a
'hand crafted' (smile) way, only in 0.98. Attached patch replaces that with use
of MetaScanner#metaScan so there's proper relocation should META's location be
cached and stale.
was (Author: apurtell):
HBaseAdmin#deleteTable, when determining if table regions are still in the
catalog, would contact the regionserver hosting meta directly for scanning in a
'hand crafted' (smile) way, only in 0.98. Attached patch replaces that with use
of MetaScanner#metaScan so there's proper relocation should META's location be
cached.
> HBaseAdmin#deleteTable should relocate META when cached location is stale
> -------------------------------------------------------------------------
>
> Key: HBASE-14453
> URL: https://issues.apache.org/jira/browse/HBASE-14453
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.14
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.98.15
>
> Attachments: HBASE-14453-0.98.patch
>
>
> After HBASE-14275, in HBaseAdmin#deleteTable, when using MetaReader to wait
> until all regions are deleted, we won't attempt to relocate META should its
> cached location be stale.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
