[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-13 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473563#comment-16473563
 ] 

Hadoop QA commented on HBASE-20566:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
16s{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} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
44s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
36s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
11s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
50s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
37s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
17s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  4m 
40s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
32s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
11s{color} | {color:green} the patch passed {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}  4m 
47s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
14m 33s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
42s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
16s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  3m 
16s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
 9s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 41m 18s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f |
| JIRA Issue | HBASE-20566 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12923210/HBASE-20566.master.002.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  shadedjars  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux f5992a8fefc5 3.13.0-139-generic #188-Ubuntu SMP Tue Jan 9 
14:43:09 UTC 2018 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 021f66d11d |
| maven | version: Apache Maven 3.5.3 
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_171 |
| findbugs | v3.1.0-RC3 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/12802/testReport/ |
| Max. process+thread count | 1883 (vs. ulimit of 1) |
| modules | C: hbase-rsgroup U: hbase-rsgroup |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/12802/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> Creating a system 

[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-13 Thread Nihal Jain (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473552#comment-16473552
 ] 

Nihal Jain commented on HBASE-20566:


I have moved quota enabling to {{setUp()}}. Now, we don't need to re-start 
hbase at all, as it does is unnecessary to disable quota at the end of 
{{testRSGroupsWithHBaseQuota()}}.

Please review the changes.

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20566.master.001.patch, 
> HBASE-20566.master.002.patch
>
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-13 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473517#comment-16473517
 ] 

Ted Yu commented on HBASE-20566:


The fix would be checked in, so I don't anticipate negative impact on the rest 
of the tests.

Please move enabling of quota to setUp() in your next patch.

Thanks

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20566.master.001.patch
>
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-13 Thread Nihal Jain (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473413#comment-16473413
 ] 

Nihal Jain commented on HBASE-20566:


{quote}I think the enabling of quota can be done in setUp() method so that we 
don't need to restart the cluster twice.
{quote}
I had written the test case in a way that it does not hinder the result of any 
other test cases in the given class. Enabling quota in the set up can be done, 
but say we run the test class without the fix (i.e. if quota table creation 
gets stuck), then none of the test cases would pass as the bug for some reasons 
fails dropping of tables and rolls back. Hence will cause all test cases to 
fail.
{code:java}
2018-05-13 14:16:02,171 INFO  
[RpcServer.default.FPBQ.Fifo.handler=29,queue=2,port=16000] master.HMaster: 
Client=root1//127.0.0.1 delete test
2018-05-13 14:16:02,287 INFO  
[RpcServer.default.FPBQ.Fifo.handler=29,queue=2,port=16000] 
rsgroup.RSGroupAdminServer: Moving table test to RSGroup null
2018-05-13 14:16:02,292 INFO  [PEWorker-16] hbase.MetaTableAccessor: Deleted 1 
regions from META
2018-05-13 14:16:02,307 INFO  [PEWorker-16] hbase.MetaTableAccessor: Deleted 1 
regions from META
2018-05-13 14:16:02,309 INFO  [PEWorker-16] hbase.MetaTableAccessor: Deleted 
table test state from META
2018-05-13 14:16:02,313 INFO  [PEWorker-16] procedure2.ProcedureExecutor: 
Finished pid=20, state=SUCCESS; DeleteTableProcedure table=test in 140msec
2018-05-13 14:16:07,045 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:12,045 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:17,046 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:22,046 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:27,046 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:32,046 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:37,047 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:42,047 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:47,048 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:52,049 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:16:57,049 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:17:02,050 WARN  [ProcExecTimeout] assignment.AssignmentManager: 
STUCK Region-In-Transition rit=OFFLINE, location=localhost,1,1, 
table=hbase:quota, region=2b9f9ceca3cb8a77ae2220b053c1c4e7
2018-05-13 14:17:02,282 INFO  
[RpcServer.default.FPBQ.Fifo.handler=28,queue=1,port=16000] master.HMaster: 
Client=root1//127.0.0.1 delete test
2018-05-13 14:17:02,411 INFO  [PEWorker-3] procedure2.ProcedureExecutor: Rolled 
back pid=21, state=ROLLEDBACK, 
exception=org.apache.hadoop.hbase.TableNotFoundException via 
master-delete-table:org.apache.hadoop.hbase.TableNotFoundException: test; 
DeleteTableProcedure table=test exec-time=128msec
{code}

Since with the fix the test case will pass, we can surely move enabling of 
quota to setUp(), but am not sure about negative scenarios. What do you suggest?

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Assignee: Nihal Jain
>   

[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-12 Thread Hadoop QA (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473308#comment-16473308
 ] 

Hadoop QA commented on HBASE-20566:
---

| (/) *{color:green}+1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m 
20s{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} master Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
43s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
22s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} shadedjars {color} | {color:green}  4m 
54s{color} | {color:green} branch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  0m 
55s{color} | {color:green} master passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
28s{color} | {color:green} master passed {color} |
|| || || || {color:brown} Patch Compile Tests {color} ||
| {color:green}+1{color} | {color:green} mvninstall {color} | {color:green}  5m 
 6s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} compile {color} | {color:green}  0m 
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javac {color} | {color:green}  0m 
43s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} checkstyle {color} | {color:green}  0m 
13s{color} | {color:green} the patch passed {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}  4m 
15s{color} | {color:green} patch has no errors when building our shaded 
downstream artifacts. {color} |
| {color:green}+1{color} | {color:green} hadoopcheck {color} | {color:green} 
15m 10s{color} | {color:green} Patch does not cause any errors with Hadoop 
2.6.5 2.7.4 or 3.0.0. {color} |
| {color:green}+1{color} | {color:green} findbugs {color} | {color:green}  1m 
27s{color} | {color:green} the patch passed {color} |
| {color:green}+1{color} | {color:green} javadoc {color} | {color:green}  0m 
24s{color} | {color:green} the patch passed {color} |
|| || || || {color:brown} Other Tests {color} ||
| {color:green}+1{color} | {color:green} unit {color} | {color:green}  5m 
22s{color} | {color:green} hbase-rsgroup in the patch passed. {color} |
| {color:green}+1{color} | {color:green} asflicense {color} | {color:green}  0m 
10s{color} | {color:green} The patch does not generate ASF License warnings. 
{color} |
| {color:black}{color} | {color:black} {color} | {color:black} 46m 58s{color} | 
{color:black} {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/hbase:d8b550f |
| JIRA Issue | HBASE-20566 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12923180/HBASE-20566.master.001.patch
 |
| Optional Tests |  asflicense  javac  javadoc  unit  findbugs  shadedjars  
hadoopcheck  hbaseanti  checkstyle  compile  |
| uname | Linux 2d4f6c293227 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 
12:16:42 UTC 2017 x86_64 GNU/Linux |
| Build tool | maven |
| Personality | 
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/component/dev-support/hbase-personality.sh
 |
| git revision | master / 021f66d11d |
| maven | version: Apache Maven 3.5.3 
(3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T19:49:05Z) |
| Default Java | 1.8.0_171 |
| findbugs | v3.1.0-RC3 |
|  Test Results | 
https://builds.apache.org/job/PreCommit-HBASE-Build/12799/testReport/ |
| Max. process+thread count | 2785 (vs. ulimit of 1) |
| modules | C: hbase-rsgroup U: hbase-rsgroup |
| Console output | 
https://builds.apache.org/job/PreCommit-HBASE-Build/12799/console |
| Powered by | Apache Yetus 0.7.0   http://yetus.apache.org |


This message was automatically generated.



> Creating a system 

[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-12 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473304#comment-16473304
 ] 

Ted Yu commented on HBASE-20566:


I think the enabling of quota can be done in setUp() method so that we don't 
need to restart the cluster twice.

On my Mac, the duration for TestRSGroups went from 182 seconds to 166 seconds.

You just need to adjust the assertion in basic test:
{code}
-//3 meta,namespace, group
-assertEquals(3, count);
+//3 meta,namespace, rsgroup, quota
+assertEquals(4, count);
{code}
This also proves that all assertions in previous tests still hold with quota 
enabled.

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20566.master.001.patch
>
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-12 Thread Nihal Jain (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473301#comment-16473301
 ] 

Nihal Jain commented on HBASE-20566:


Hi [~yuzhih...@gmail.com], they are also doing it in a similar way. Right?
{code:java}
.
.
LOG.info("Shutting down cluster");
UTIL.shutdownMiniHBaseCluster();

Thread.sleep(2000);
LOG.info("Starting cluster again with FN Balancer");
UTIL.getConfiguration().set(HConstants.HBASE_MASTER_LOADBALANCER_CLASS,
FavoredStochasticBalancer.class.getName());
UTIL.restartHBaseCluster(SLAVES);
while (!UTIL.getMiniHBaseCluster().getMaster().isInitialized()) {
Threads.sleep(1);
}
.
.{code}

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Assignee: Nihal Jain
>Priority: Major
> Fix For: 3.0.0
>
> Attachments: HBASE-20566.master.001.patch
>
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-12 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16473206#comment-16473206
 ] 

Ted Yu commented on HBASE-20566:


I wonder if adding postCreateTable hook to 
hbase-server/src/main/java/org/apache/hadoop/hbase/quotas/MasterSpaceQuotaObserver.java
 would help solve the issue.

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Assignee: Nihal Jain
>Priority: Major
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-12 Thread Nihal Jain (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472977#comment-16472977
 ] 

Nihal Jain commented on HBASE-20566:


I think we can. Will try and update soon. And thanks for the reference, seems 
useful. Will look into it.

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Priority: Major
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-11 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16472755#comment-16472755
 ] 

Ted Yu commented on HBASE-20566:


Can this problem be re-created with unit test ?

Please see also HBASE-19757

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Priority: Major
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-11 Thread Nihal Jain (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471662#comment-16471662
 ] 

Nihal Jain commented on HBASE-20566:


Dug a little deep. Points to note:
 * During "hbase:quota" table creation, the CreateTableProcedure stays in 
WAITING state as the child procedure AssignProcedure tries to assign table 
regions
 * The postCreateTable() hook is not reached which actually does default RS 
group assignment for each table.
 * None of the CreateTableProcedure hooks seem to be idle place for the logic 
to add the current system table to rsgroup

Wondering where this logic should go!

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Priority: Major
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-10 Thread Nihal Jain (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471503#comment-16471503
 ] 

Nihal Jain commented on HBASE-20566:


We can handle this by adding the logic to add system tables to appropriate ** 
rsgroup ** in *preCreateTableAction()*

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Priority: Major
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (HBASE-20566) Creating a system table after enabling rsgroup feature puts in region into RIT

2018-05-10 Thread Ted Yu (JIRA)

[ 
https://issues.apache.org/jira/browse/HBASE-20566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16471163#comment-16471163
 ] 

Ted Yu commented on HBASE-20566:


Interesting.

Do you want to work out a patch ?

Thanks

> Creating a system table after enabling rsgroup feature puts in region into RIT
> --
>
> Key: HBASE-20566
> URL: https://issues.apache.org/jira/browse/HBASE-20566
> Project: HBase
>  Issue Type: Bug
>  Components: master
>Reporter: Biju Nair
>Priority: Major
>
> *Steps to reproduce*
>  - Enable {{rsgroup}} feature
>  - Enable {{quota}} feature which created {{hbase::quota}} table
>  - quota table region will be marked as RIT since the {{rsgroup}} for the 
> table is not known
> {noformat}
> 2018-05-10 14:33:32,392 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from null to 
> ENABLING
> 2018-05-10 14:33:32,397 WARN  [ProcedureExecutorThread-0] 
> rsgroup.RSGroupBasedLoadBalancer: Group for table hbase:quota is null
> 2018-05-10 14:33:32,398 WARN  [ProcedureExecutorThread-0] 
> master.RegionStates: Failed to open/close 89490cd5e00ea8948af413a1df65091a on 
> null, set to FAILED_OPEN
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> master.RegionStates: Transition {89490cd5e00ea8948af413a1df65091a 
> state=OFFLINE, ts=1525977212397, server=null} to 
> {89490cd5e00ea8948af413a1df65091a state=FAILED_OPEN, ts=1525977212398, 
> server=null}
> 2018-05-10 14:33:32,398 INFO  [ProcedureExecutorThread-0] 
> zookeeper.ZKTableStateManager: Moving table hbase:quota state from ENABLING 
> to ENABLED
> {noformat}
>  - Reason for this issue: Issue
>  - [system table 
> creation|https://github.com/apache/hbase/blob/061a31fad1654d9ded96d118e04c14860413fa25/hbase-server/src/main/java/org/apache/hadoop/hbase/master/HMaster.java#L1793]
>  doesn't move the table to the appropriate rs group to which system namespace 
> is assigned to. Need to execute logic similar to what is done in the 
> RSGroupAdminEndpoint for [post table creation|#L377] for user table creation.
> *Work Around*
>   - Assigning the system table to ``default`` rsgroup (or to the rsgroup to 
> which the system namespace has been assigned).
>   - Manually assigning the region in RIT from the system table
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)