[jira] [Commented] (HBASE-22142) Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
[
https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934850#comment-16934850
]
Hudson commented on HBASE-22142:
Results for branch master
[build #1469 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1469/]: (x)
*{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1469//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1469//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1469//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Space quota: If table inside namespace having space quota is dropped, data
> size usage is still considered for the drop table.
> --
>
> Key: HBASE-22142
> URL: https://issues.apache.org/jira/browse/HBASE-22142
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: Shardul Singh
>Assignee: Shardul Singh
>Priority: Minor
> Labels: Quota, space
> Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
> Attachments: HBASE-22142.branch-2.1.v001.patch
>
>
> steps to follow:
> 1.create a quota at namespace level
> 2.create 2 tables t1 and t2 inside namespace and write data.
> 3.write 5 mb of data each in both t1 and t2.
> 4. drop t1.
> 5. data usage for t2 will be shown 10 mb for 10 minutes.
> If table is dropped inside namespace, data size usage is still shown for 10
> minutes because of the configuration
> "hbase.master.quotas.region.report.retention.millis". This conf maintains the
> region report in cache(regionSizes) and old entry is used for 10 minutes. We
> can remove the entry from cache during the drop command as part of MasterCP
> hook only, so that correct usage is show instantaneously after the drop
> command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-22142) Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
[
https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934843#comment-16934843
]
Hudson commented on HBASE-22142:
Results for branch branch-2.2
[build #630 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/630/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/630//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/630//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/630//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Space quota: If table inside namespace having space quota is dropped, data
> size usage is still considered for the drop table.
> --
>
> Key: HBASE-22142
> URL: https://issues.apache.org/jira/browse/HBASE-22142
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: Shardul Singh
>Assignee: Shardul Singh
>Priority: Minor
> Labels: Quota, space
> Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
> Attachments: HBASE-22142.branch-2.1.v001.patch
>
>
> steps to follow:
> 1.create a quota at namespace level
> 2.create 2 tables t1 and t2 inside namespace and write data.
> 3.write 5 mb of data each in both t1 and t2.
> 4. drop t1.
> 5. data usage for t2 will be shown 10 mb for 10 minutes.
> If table is dropped inside namespace, data size usage is still shown for 10
> minutes because of the configuration
> "hbase.master.quotas.region.report.retention.millis". This conf maintains the
> region report in cache(regionSizes) and old entry is used for 10 minutes. We
> can remove the entry from cache during the drop command as part of MasterCP
> hook only, so that correct usage is show instantaneously after the drop
> command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-22142) Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
[
https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934820#comment-16934820
]
Hudson commented on HBASE-22142:
Results for branch branch-2
[build #2289 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2289/]:
(x) *{color:red}-1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2289//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2289//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2/2289//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Space quota: If table inside namespace having space quota is dropped, data
> size usage is still considered for the drop table.
> --
>
> Key: HBASE-22142
> URL: https://issues.apache.org/jira/browse/HBASE-22142
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: Shardul Singh
>Assignee: Shardul Singh
>Priority: Minor
> Labels: Quota, space
> Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
> Attachments: HBASE-22142.branch-2.1.v001.patch
>
>
> steps to follow:
> 1.create a quota at namespace level
> 2.create 2 tables t1 and t2 inside namespace and write data.
> 3.write 5 mb of data each in both t1 and t2.
> 4. drop t1.
> 5. data usage for t2 will be shown 10 mb for 10 minutes.
> If table is dropped inside namespace, data size usage is still shown for 10
> minutes because of the configuration
> "hbase.master.quotas.region.report.retention.millis". This conf maintains the
> region report in cache(regionSizes) and old entry is used for 10 minutes. We
> can remove the entry from cache during the drop command as part of MasterCP
> hook only, so that correct usage is show instantaneously after the drop
> command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-22142) Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
[
https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16934812#comment-16934812
]
Hudson commented on HBASE-22142:
Results for branch branch-2.1
[build #1626 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1626/]:
(/) *{color:green}+1 overall{color}*
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1626//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1626//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.1/1626//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Space quota: If table inside namespace having space quota is dropped, data
> size usage is still considered for the drop table.
> --
>
> Key: HBASE-22142
> URL: https://issues.apache.org/jira/browse/HBASE-22142
> Project: HBase
> Issue Type: Bug
>Affects Versions: 2.1.1
>Reporter: Shardul Singh
>Assignee: Shardul Singh
>Priority: Minor
> Labels: Quota, space
> Fix For: 3.0.0, 2.3.0, 2.1.7, 2.2.2
>
> Attachments: HBASE-22142.branch-2.1.v001.patch
>
>
> steps to follow:
> 1.create a quota at namespace level
> 2.create 2 tables t1 and t2 inside namespace and write data.
> 3.write 5 mb of data each in both t1 and t2.
> 4. drop t1.
> 5. data usage for t2 will be shown 10 mb for 10 minutes.
> If table is dropped inside namespace, data size usage is still shown for 10
> minutes because of the configuration
> "hbase.master.quotas.region.report.retention.millis". This conf maintains the
> region report in cache(regionSizes) and old entry is used for 10 minutes. We
> can remove the entry from cache during the drop command as part of MasterCP
> hook only, so that correct usage is show instantaneously after the drop
> command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (HBASE-22142) Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
[
https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908604#comment-16908604
]
HBase QA commented on HBASE-22142:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
39s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} branch-2.1 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
59s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
50s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
8s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
53s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
11s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
30s{color} | {color:green} branch-2.1 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
28s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
6s{color} | {color:red} hbase-server: The patch generated 4 new + 4 unchanged -
0 fixed = 8 total (was 4) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
49s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
20m 23s{color} | {color:green} Patch does not cause any errors with Hadoop
2.7.7 2.8.5 or 3.0.3 3.1.2. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
34s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
32s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}139m 14s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
22s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}192m 51s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.snapshot.TestFlushSnapshotFromClient |
| | hadoop.hbase.snapshot.TestMobFlushSnapshotFromClient |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=19.03.1 Server=19.03.1 base:
https://builds.apache.org/job/PreCommit-HBASE-Build/780/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-22142 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12965440/HBASE-22142.branch-2.1.v001.patch
|
| Optional Tests | dupname asflicense javac javadoc unit findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 8c11033e13cd 4.4.0-139-generic #165-Ubuntu SMP Wed Oct 24
10:58:50 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/hbase-personality.sh |
| git revision | branch-2.1 / 0481b04ca3 |
| maven | version: Apache Maven 3.5.4
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.11 |
| checkstyle |
https://builds.apache.org/job/PreCommit-HBASE-Build/780/artifact/patchprocess/diff-checkstyle-hbase-server.txt
|
| unit |
https://builds.
[jira] [Commented] (HBASE-22142) Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
[ https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908514#comment-16908514 ] Sakthi commented on HBASE-22142: Reviewing. > Space quota: If table inside namespace having space quota is dropped, data > size usage is still considered for the drop table. > -- > > Key: HBASE-22142 > URL: https://issues.apache.org/jira/browse/HBASE-22142 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: Shardul Singh >Assignee: Shardul Singh >Priority: Minor > Labels: Quota, space > Attachments: HBASE-22142.branch-2.1.v001.patch > > > steps to follow: > 1.create a quota at namespace level > 2.create 2 tables t1 and t2 inside namespace and write data. > 3.write 5 mb of data each in both t1 and t2. > 4. drop t1. > 5. data usage for t2 will be shown 10 mb for 10 minutes. > If table is dropped inside namespace, data size usage is still shown for 10 > minutes because of the configuration > "hbase.master.quotas.region.report.retention.millis". This conf maintains the > region report in cache(regionSizes) and old entry is used for 10 minutes. We > can remove the entry from cache during the drop command as part of MasterCP > hook only, so that correct usage is show instantaneously after the drop > command. -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Commented] (HBASE-22142) Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
[
https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814543#comment-16814543
]
HBase QA commented on HBASE-22142:
--
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 1m
14s{color} | {color:blue} Docker mode activated. {color} |
|| || || || {color:brown} Prechecks {color} ||
| {color:green}+1{color} | {color:green} hbaseanti {color} | {color:green} 0m
0s{color} | {color:green} Patch does not have any anti-patterns. {color} |
| {color:green}+1{color} | {color:green} @author {color} | {color:green} 0m
0s{color} | {color:green} The patch does not contain any @author tags. {color} |
| {color:green}+1{color} | {color:green} test4tests {color} | {color:green} 0m
0s{color} | {color:green} The patch appears to include 1 new or modified test
files. {color} |
|| || || || {color:brown} branch-2.1 Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 4m
30s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
52s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green} 1m
8s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 4m
12s{color} | {color:green} branch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
16s{color} | {color:green} branch-2.1 passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
31s{color} | {color:green} branch-2.1 passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green} 3m
52s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green} 0m
47s{color} | {color:green} the patch passed {color} |
| {color:red}-1{color} | {color:red} checkstyle {color} | {color:red} 1m
5s{color} | {color:red} hbase-server: The patch generated 4 new + 4 unchanged -
0 fixed = 8 total (was 4) {color} |
| {color:green}+1{color} | {color:green} whitespace {color} | {color:green} 0m
0s{color} | {color:green} The patch has no whitespace issues. {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green} 3m
53s{color} | {color:green} patch has no errors when building our shaded
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green}
8m 14s{color} | {color:green} Patch does not cause any errors with Hadoop 2.7.4
or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green} 2m
17s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green} 0m
28s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:red}-1{color} | {color:red} unit {color} | {color:red}225m 5s{color}
| {color:red} hbase-server in the patch failed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green} 0m
30s{color} | {color:green} The patch does not generate ASF License warnings.
{color} |
| {color:black}{color} | {color:black} {color} | {color:black}261m 41s{color} |
{color:black} {color} |
\\
\\
|| Reason || Tests ||
| Failed junit tests | hadoop.hbase.client.TestFromClientSideWithCoprocessor |
| | hadoop.hbase.client.TestFromClientSide |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce base:
https://builds.apache.org/job/PreCommit-HBASE-Build/50/artifact/patchprocess/Dockerfile
|
| JIRA Issue | HBASE-22142 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12965440/HBASE-22142.branch-2.1.v001.patch
|
| Optional Tests | dupname asflicense javac javadoc unit findbugs
shadedjars hadoopcheck hbaseanti checkstyle compile |
| uname | Linux 19f5b3105d8b 4.4.0-137-generic #163-Ubuntu SMP Mon Sep 24
13:14:43 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | dev-support/hbase-personality.sh |
| git revision | branch-2.1 / 4ceffc83fe |
| maven | version: Apache Maven 3.5.4
(1edded0938998edf8bf061f1ceb3cfdeccf443fe; 2018-06-17T18:33:14Z) |
| Default Java | 1.8.0_181 |
| findbugs | v3.1.11 |
| checkstyle |
https://builds.apache.org/job/PreCommit-HBASE-Build/50/artifact/patchprocess/diff-checkstyle-hbase-server.txt
|
| unit |
https://builds.apache.org/job/Pre
[jira] [Commented] (HBASE-22142) Space quota: If table inside namespace having space quota is dropped, data size usage is still considered for the drop table.
[ https://issues.apache.org/jira/browse/HBASE-22142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16809659#comment-16809659 ] Shardul Singh commented on HBASE-22142: --- I would like to work on this issue..Can someone assign it to me:) > Space quota: If table inside namespace having space quota is dropped, data > size usage is still considered for the drop table. > -- > > Key: HBASE-22142 > URL: https://issues.apache.org/jira/browse/HBASE-22142 > Project: HBase > Issue Type: Bug >Affects Versions: 2.1.1 >Reporter: Shardul Singh >Priority: Minor > > steps to follow: > 1.create a quota at namespace level > 2.create 2 tables t1 and t2 inside namespace and write data. > 3.write 5 mb of data each in both t1 and t2. > 4. drop t1. > 5. data usage for t2 will be shown 10 mb for 10 minutes. > If table is dropped inside namespace, data size usage is still shown for 10 > minutes because of the configuration > "hbase.master.quotas.region.report.retention.millis". This conf maintains the > region report in cache(regionSizes) and old entry is used for 10 minutes. We > can remove the entry during the drop command only, so that correct usage is > show instantaneously after the drop command. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
