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

Hudson commented on HBASE-21866:
--------------------------------

Results for branch branch-1
        [build #686 on 
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/686/]: 
(x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/686//General_Nightly_Build_Report/]


(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7 
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-1/686//JDK7_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-1/686//JDK8_Nightly_Build_Report_(Hadoop2)/]




(x) {color:red}-1 source release artifact{color}
-- See build output for details.


> Do not move the table to null rsgroup when creating an existing table
> ---------------------------------------------------------------------
>
>                 Key: HBASE-21866
>                 URL: https://issues.apache.org/jira/browse/HBASE-21866
>             Project: HBase
>          Issue Type: Bug
>          Components: proc-v2, rsgroup
>            Reporter: Xiang Li
>            Assignee: Xiang Li
>            Priority: Major
>         Attachments: HBASE-21866.branch-1.000.patch, 
> HBASE-21866.master.000.patch, HBASE-21866.master.001.patch, 
> HBASE-21866.master.002.patch, HBASE-21866.master.003.patch, 
> HBASE-21866.master.003.patch, HBASE-21866.master.003.patch
>
>
> By using the latest HBase master branch, the bug could be re-produced as:
>  # create 't1', 'cf1'
>  # create 't1', 'cf1'
> The following message is logged into HMaster's log:
> {code}
> INFO  [PEWorker-12] rsgroup.RSGroupAdminServer: Moving table t1 to RSGroup 
> null
> {code}
> This is a wrong action and instead, we should keep t1 as where it originally 
> is.



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

Reply via email to