[
https://issues.apache.org/jira/browse/HBASE-22417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wellington Chevreuil updated HBASE-22417:
-----------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Latest test failure is unrelated. Pushed to master, branch-2, branch-2.1 and
branch-2.2 branches. Thanks for reviewing it, [~stack]!
> DeleteTableProcedure.deleteFromMeta method should remove table from Master's
> table descriptors cache
> ----------------------------------------------------------------------------------------------------
>
> Key: HBASE-22417
> URL: https://issues.apache.org/jira/browse/HBASE-22417
> Project: HBase
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.2.0, 2.1.5
> Reporter: Wellington Chevreuil
> Assignee: Wellington Chevreuil
> Priority: Major
> Fix For: 3.0.0, 2.2.1, 2.1.6
>
> Attachments: HBASE-22417.master.001.patch,
> HBASE-22417.master.002.patch, HBASE-22417.master.003.patch,
> HBASE-22417.master.004.patch, HBASE-22417.master.005.patch
>
>
> DeleteTableProcedure defines a static deleteFromMeta method that's currently
> used both by DeleteTableProcedure itself and TruncateTableProcedure.
> Sometimes, depending on the table size (and under slower, under performing
> FileSystems), truncation can take longer to complete
> *TRUNCATE_TABLE_CLEAR_FS_LAYOUT* stage, but the given table has already been
> deleted from meta on previous *TRUNCATE_TABLE_REMOVE_FROM_META* stage. In
> this case, features relying on Master's table descriptor's cache might
> wrongly try to reference this truncating table. Master Web UI, for example,
> would try to check this table state and end up showing a 500 error.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
