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

Hadoop QA commented on HBASE-14682:
-----------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12768167/hbase-14682_v1.patch
  against master branch at commit 36d4a5a650ceead3be5012cdd25dc35efa383755.
  ATTACHMENT ID: 12768167

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified tests.

    {color:green}+1 hadoop versions{color}. The patch compiles with all 
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.6.1 2.7.0 
2.7.1)

    {color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

    {color:green}+1 protoc{color}.  The applied patch does not increase the 
total number of protoc compiler warnings.

    {color:green}+1 javadoc{color}.  The javadoc tool did not generate any 
warning messages.

    {color:green}+1 checkstyle{color}.  The applied patch does not increase the 
total number of checkstyle errors

    {color:green}+1 findbugs{color}.  The patch does not introduce any  new 
Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines 
longer than 100

  {color:green}+1 site{color}.  The mvn post-site goal succeeds with this patch.

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results: 
https://builds.apache.org/job/PreCommit-HBASE-Build/16184//testReport/
Release Findbugs (version 2.0.3)        warnings: 
https://builds.apache.org/job/PreCommit-HBASE-Build/16184//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: 
https://builds.apache.org/job/PreCommit-HBASE-Build/16184//artifact/patchprocess/checkstyle-aggregate.html

  Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/16184//console

This message is automatically generated.

> CM restore functionality for regionservers is broken
> ----------------------------------------------------
>
>                 Key: HBASE-14682
>                 URL: https://issues.apache.org/jira/browse/HBASE-14682
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>         Attachments: hbase-14682_v1.patch
>
>
> In the {{DistributedHBaseCluster.restoreClusterStatus()}}, we are starting a 
> regionserver for backup masters. Seems to be a copy-paste error from 
> HBASE-12429. 
> This is causing further issues on our test rig since we are starting a 
> regionserver where only a backup master were before:
> {code}
> INFO  [main] hbase.HBaseClusterManager: Executing remote command: ps aux | 
> grep proc_master | grep -v grep | tr -s ' ' | cut -d ' ' -f2 , 
> hostname:10.0.0.99
> INFO  [main] util.Shell: Executing full command [/usr/bin/ssh  -o 
> StrictHostKeyChecking=no 10.0.0.99 "sudo su - hbase -c \"ps aux | grep 
> proc_master | grep -v grep | tr -s ' ' | cut -d ' ' -f2\""]
> INFO  [main] hbase.HBaseClusterManager: Executed remote command, exit code:0 
> , output:13244
> INFO  [main] hbase.HBaseClusterManager: Executing remote command: ps aux | 
> grep proc_regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2 , 
> hostname:10.0.0.99
> INFO  [main] util.Shell: Executing full command [/usr/bin/ssh  -o 
> StrictHostKeyChecking=no 10.0.0.99 "sudo su - hbase -c \"ps aux | grep 
> proc_regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2\""]
> INFO  [main] hbase.HBaseClusterManager: Executed remote command, exit code:0 
> , output:
> INFO  [main] hbase.HBaseCluster: Restoring cluster - starting initial region 
> server: 10.0.0.99:16000
> INFO  [main] hbase.HBaseCluster: Starting RS on: 10.0.0.99
> INFO  [main] hbase.HBaseClusterManager: Executing remote command: 
> /usr/hdp/2.3.3.0-2971/hbase/bin/hbase-daemon.sh --config /tmp/hbaseConf start 
> regionserver , hostname:10.0.0.99
> INFO  [main] util.Shell: Executing full command [/usr/bin/ssh  -o 
> StrictHostKeyChecking=no 10.0.0.99 "sudo su - hbase -c 
> \"/usr/hdp/2.3.3.0-2971/hbase/bin/hbase-daemon.sh --config /tmp/hbaseConf 
> start reg
> INFO  [main] hbase.HBaseClusterManager: Executed remote command, exit code:0 
> , output:starting regionserver, logging to 
> /var/log/hbase/hbase-hbase-regionserver-zk0-hb23-h.out
> INFO  [main] hbase.HBaseClusterManager: Executing remote command: ps aux | 
> grep proc_regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2 , 
> hostname:10.0.0.126
> INFO  [main] util.Shell: Executing full command [/usr/bin/ssh  -o 
> StrictHostKeyChecking=no 10.0.0.126 "sudo su - hbase -c \"ps aux | grep 
> proc_regionserver | grep -v grep | tr -s ' ' | cut -d ' ' -f2\""]
> INFO  [main] hbase.HBaseClusterManager: Executed remote command, exit code:0 
> , output:
> INFO  [main] hbase.HBaseCluster: Added new HBaseAdmin
> INFO  [main] hbase.HBaseCluster: Restoring cluster - done
> DEBUG [main] hbase.IntegrationTestBase: Done restoring the cluster
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to