[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15013435#comment-15013435
]
Hudson commented on HBASE-14805:
FAILURE: Integrated in HBase-0.98-on-Hadoop-1.1 #1135 (See
[https://builds.apache.org/job/HBase-0.98-on-Hadoop-1.1/1135/])
HBASE-14805 status should show the master in shell (enis: rev
5fe779a61245167176ffacc0af810866597d4275)
* hbase-shell/src/main/ruby/hbase/admin.rb
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch, hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15013489#comment-15013489
]
Hudson commented on HBASE-14805:
FAILURE: Integrated in HBase-0.98-matrix #262 (See
[https://builds.apache.org/job/HBase-0.98-matrix/262/])
HBASE-14805 status should show the master in shell (enis: rev
5fe779a61245167176ffacc0af810866597d4275)
* hbase-shell/src/main/ruby/hbase/admin.rb
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch, hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15012772#comment-15012772
]
Hudson commented on HBASE-14805:
FAILURE: Integrated in HBase-Trunk_matrix #479 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/479/])
HBASE-14805 status should show the master in shell (enis: rev
b2c20cebb013060f3e81ad22b38841e865a5ba9a)
* hbase-shell/src/main/ruby/hbase/admin.rb
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch, hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15012779#comment-15012779
]
Hudson commented on HBASE-14805:
SUCCESS: Integrated in HBase-1.2-IT #291 (See
[https://builds.apache.org/job/HBase-1.2-IT/291/])
HBASE-14805 status should show the master in shell (enis: rev
ac92762d3bcc283dbb181819abb8e562f89f1de1)
* hbase-shell/src/main/ruby/hbase/admin.rb
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch, hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15012759#comment-15012759
]
Hudson commented on HBASE-14805:
FAILURE: Integrated in HBase-1.3-IT #321 (See
[https://builds.apache.org/job/HBase-1.3-IT/321/])
HBASE-14805 status should show the master in shell (enis: rev
98f7dcc3896ac846dc834b7c50567f1de0d44231)
* hbase-shell/src/main/ruby/hbase/admin.rb
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch, hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15012961#comment-15012961
]
Hudson commented on HBASE-14805:
FAILURE: Integrated in HBase-1.2 #384 (See
[https://builds.apache.org/job/HBase-1.2/384/])
HBASE-14805 status should show the master in shell (enis: rev
ac92762d3bcc283dbb181819abb8e562f89f1de1)
* hbase-shell/src/main/ruby/hbase/admin.rb
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch, hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15012734#comment-15012734
]
Hudson commented on HBASE-14805:
SUCCESS: Integrated in HBase-1.3 #378 (See
[https://builds.apache.org/job/HBase-1.3/378/])
HBASE-14805 status should show the master in shell (enis: rev
98f7dcc3896ac846dc834b7c50567f1de0d44231)
* hbase-shell/src/main/ruby/hbase/admin.rb
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch, hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15007461#comment-15007461
]
Hadoop QA commented on HBASE-14805:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12772563/hbase-14805_v1.patch
against master branch at commit f218e499ae12805cc35ed938c1f6d07ace048a25.
ATTACHMENT ID: 12772563
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{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:red}-1 lineLengths{color}. The patch introduces the following lines
longer than 100:
+puts("active master: %s:%d %d" % [master.getHostname(),
master.getPort(), master.getStartcode()])
+puts("active master: %s:%d %d" % [master.getHostname(),
master.getPort(), master.getStartcode()])
+puts "1 active master, #{status.getBackupMastersSize} backup masters,
#{status.getServersSize} servers, #{status.getDeadServers} dead, #{'%.4f' %
status.getAverageLoad} average load"
{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/16537//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/16537//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/16537//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/16537//console
This message is automatically generated.
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch, hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15005753#comment-15005753
]
Andrew Purtell commented on HBASE-14805:
+1 on the patch provided it passes a precommit build
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0, 0.98.17
>
> Attachments: hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003458#comment-15003458
]
Hadoop QA commented on HBASE-14805:
---
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12772098/hbase-14805_v1.patch
against master branch at commit 789f8a5a70242c16ce10bc95401c51c7d04debfa.
ATTACHMENT ID: 12772098
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:red}-1 tests included{color}. The patch doesn't appear to include
any new or modified tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
{color:red}-1 javac{color}. The patch appears to cause mvn compile goal to
fail with Hadoop version 2.5.0.
Compilation errors resume:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-clean-plugin:2.5:clean (default-clean) on
project hbase-server: Failed to clean project: Failed to delete
/home/jenkins/jenkins-slave/workspace/PreCommit-HBASE-Build/hbase/hbase-server/target
-> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :hbase-server
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/16505//console
This message is automatically generated.
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003447#comment-15003447
]
Romil Choksi commented on HBASE-14805:
--
[~enis]
Have you tried zk_dump command from hbase shell, it gives out active master,
backup masters and region servers
{code}
hbase(main):060:0> zk_dump
HBase is rooted at /hbase-secure
Active master address: hbase-dalm20-rc-2.novalocal,2,1447301843054
Backup master addresses:
Region server holding hbase:meta:
hbase-dalm20-rc-7.novalocal,16020,1447301860073
Region servers:
hbase-dalm20-rc-5.novalocal,16020,1447301868926
hbase-dalm20-rc-1.novalocal,16020,1447301859425
hbase-dalm20-rc-2.novalocal,16020,1447301856988
{code}
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14805) status should show the master in shell
[
https://issues.apache.org/jira/browse/HBASE-14805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15003461#comment-15003461
]
Enis Soztutar commented on HBASE-14805:
---
Thanks [~romil.choksi] for the pointer. Yeah, {{zk_dump}} gives a dump of the
cluster from zookeeper data. The 'status' command works on top of the
{{ClusterStatus}} objects obtained from the master.
> status should show the master in shell
> --
>
> Key: HBASE-14805
> URL: https://issues.apache.org/jira/browse/HBASE-14805
> Project: HBase
> Issue Type: Improvement
>Reporter: Enis Soztutar
>Assignee: Enis Soztutar
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: hbase-14805_v1.patch
>
>
> {{status 'simple'}} or {{'detailed'}} only shows the regionservers and
> regions, but not the active master. Actually, there is no way to know about
> the active masters from the shell it seems.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
