joshelser commented on a change in pull request #571: HBASE-20821 Re-creating a
dropped namespace and contained table inherits previously set space quota
settings
URL: https://github.com/apache/hbase/pull/571#discussion_r321426926
##########
File path:
hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/MasterQuotasObserver.java
##########
@@ -78,6 +79,20 @@ public void postDeleteTable(
admin.setQuota(settings);
}
}
+ } else if (quotasAtNamespace != null) {
+ // If quota present at namespace level remove the table entry from
'hbase:quota'
Review comment:
> Because even though table is dropped it's entry is still present in the
'hbase:quota' table because of the namespace quota. If we create another table
with same name inside that namespace it inherits the earlier quota settings.
That's by design, not a bug. If you set a quota on a namespace (as opposed
to a quota on the table), you would automatically get that quota for all tables
in that namespace.
This allows an organization to be given free-rule over some namespace while
still enforcing an upper-bound on the allowed resources in HBase. e.g. a
namespace space quota of 200G would allow 200G of data in any number of tables
in that namespace, not mattering which table uses that quota.
Now, if you drop a namespace and the quota still remains, that's a bug, but
I don't think that's what you're trying to solve.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
With regards,
Apache Git Services
