You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Zheng Hu (JIRA)" <ji...@apache.org> on 2019/07/30 14:04:00 UTC
[jira] [Resolved] (HBASE-22758) Remove the unneccesary info cf
deletion in DeleteTableProcedure#deleteFromMeta
[ https://issues.apache.org/jira/browse/HBASE-22758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zheng Hu resolved HBASE-22758.
------------------------------
Resolution: Fixed
Assignee: Zheng Hu
Hadoop Flags: Reviewed
Pushed to all branch-2.x & master, Thanks [~stack] for reviewing.
> Remove the unneccesary info cf deletion in DeleteTableProcedure#deleteFromMeta
> ------------------------------------------------------------------------------
>
> Key: HBASE-22758
> URL: https://issues.apache.org/jira/browse/HBASE-22758
> Project: HBase
> Issue Type: Bug
> Reporter: Zheng Hu
> Assignee: Zheng Hu
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
>
> I saw the deleteFromMeta() method in DeleteTableProcedure & TruncateTableProcedure:
> {code}
> protected static void deleteFromMeta(final MasterProcedureEnv env,
> final TableName tableName, List<RegionInfo> regions) throws IOException {
> MetaTableAccessor.deleteRegions(env.getMasterServices().getConnection(), regions);
> // Clean any remaining rows for this table.
> cleanAnyRemainingRows(env, tableName);
> // clean region references from the server manager
> env.getMasterServices().getServerManager().removeRegions(regions);
> // Clear Favored Nodes for this table
> FavoredNodesManager fnm = env.getMasterServices().getFavoredNodesManager();
> if (fnm != null) {
> fnm.deleteFavoredNodesForRegions(regions);
> }
> }
> {code}
> 1. deleteRegions : delete the info column family first;
> 2. cleanAnyRemainingRows : delete the whole row for regions then.
> In fact, we can only change to delete the whole row, no need the extra info cf deletion any more.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)