You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Benoit Sigoure (JIRA)" <ji...@apache.org> on 2012/08/03 00:23:02 UTC
[jira] [Created] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Benoit Sigoure created HBASE-6504:
-------------------------------------
Summary: Adding GC details prevents HBase from starting in non-distributed mode
Key: HBASE-6504
URL: https://issues.apache.org/jira/browse/HBASE-6504
Project: HBase
Issue Type: Bug
Affects Versions: 0.94.0
Reporter: Benoit Sigoure
Priority: Trivial
The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
{code}
$ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
false
Heap
par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
$ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
(nothing printed)
{code}
And this confuses {{bin/start-hbase.sh}} when it does
{{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
{{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Drzal updated HBASE-6504:
---------------------------------
Labels: noob (was: )
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Priority: Trivial
> Labels: noob
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Drzal updated HBASE-6504:
---------------------------------
Status: Open (was: Patch Available)
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455250#comment-13455250 ]
Hadoop QA commented on HBASE-6504:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545030/HBASE-6504.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. 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.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause mvn compile goal to fail.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestFromClientSide
org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2858//testReport/
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2858//console
This message is automatically generated.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469876#comment-13469876 ]
Hudson commented on HBASE-6504:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #8 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/8/])
HBASE-6504 Adding GC details prevents HBase from starting in non-distributed mode (Revision 1385027)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.94/bin/rolling-restart.sh
* /hbase/branches/0.94/bin/start-hbase.sh
* /hbase/branches/0.94/bin/stop-hbase.sh
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Fix For: 0.94.2, 0.96.0
>
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455211#comment-13455211 ]
Michael Drzal commented on HBASE-6504:
--------------------------------------
I always use the old style syntax since it is more portable. From the coreutils info page:
For compatibility `head' also supports an obsolete option syntax
`-COUNTOPTIONS', which is recognized only if it is specified first.
COUNT is a decimal number optionally followed by a size letter (`b',
`k', `m') as in `-c', or `l' to mean count by lines, or other option
letters (`cqv'). Scripts intended for standard hosts should use `-c
COUNT' or `-n COUNT' instead. If your script must also run on hosts
that support only the obsolete syntax, it is usually simpler to avoid
`head', e.g., by using `sed 5q' instead of `head -5'.
I can change it to "head -n 1" if you would like.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Drzal updated HBASE-6504:
---------------------------------
Attachment: HBASE-6504-v2.patch
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453971#comment-13453971 ]
Michael Drzal commented on HBASE-6504:
--------------------------------------
I can pick this up in the next day or two. This should be a quick fix.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Drzal updated HBASE-6504:
---------------------------------
Status: Patch Available (was: Open)
Fixed this for rolling-restart.sh, start-hbase.sh, and stop-hbase.sh by using head -1 to take the first line.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456141#comment-13456141 ]
Michael Drzal commented on HBASE-6504:
--------------------------------------
Changed it to head -n 1 since this is the second time this came up in the review, and I don't care either way.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Drzal updated HBASE-6504:
---------------------------------
Attachment: HBASE-6504-output.txt
Shows output with/without gc args
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Drzal updated HBASE-6504:
---------------------------------
Attachment: HBASE-6504.patch
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456358#comment-13456358 ]
Hudson commented on HBASE-6504:
-------------------------------
Integrated in HBase-0.94 #470 (See [https://builds.apache.org/job/HBase-0.94/470/])
HBASE-6504 Adding GC details prevents HBase from starting in non-distributed mode (Revision 1385027)
Result = FAILURE
stack :
Files :
* /hbase/branches/0.94/bin/rolling-restart.sh
* /hbase/branches/0.94/bin/start-hbase.sh
* /hbase/branches/0.94/bin/stop-hbase.sh
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Fix For: 0.96.0, 0.94.3
>
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-6504:
-------------------------
Resolution: Fixed
Fix Version/s: 0.94.3
0.96.0
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk and 0.94. Thanks Michael (Thanks B and L for reviews)
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Fix For: 0.96.0, 0.94.3
>
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Drzal updated HBASE-6504:
---------------------------------
Assignee: Michael Drzal
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456190#comment-13456190 ]
Hadoop QA commented on HBASE-6504:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545213/HBASE-6504-v2.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. 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.
+1 hadoop2.0. The patch compiles against the hadoop 2.0 profile.
+1 javadoc. The javadoc tool did not generate any warning messages.
-1 javac. The patch appears to cause mvn compile goal to fail.
-1 findbugs. The patch appears to cause Findbugs (version 1.3.9) to fail.
+1 release audit. The applied patch does not increase the total number of release audit warnings.
-1 core tests. The patch failed these unit tests:
org.apache.hadoop.hbase.client.TestFromClientSideWithCoprocessor
Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2875//testReport/
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2875//console
This message is automatically generated.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456355#comment-13456355 ]
Hudson commented on HBASE-6504:
-------------------------------
Integrated in HBase-TRUNK #3337 (See [https://builds.apache.org/job/HBase-TRUNK/3337/])
HBASE-6504 Adding GC details prevents HBase from starting in non-distributed mode (Revision 1385026)
Result = FAILURE
stack :
Files :
* /hbase/trunk/bin/rolling-restart.sh
* /hbase/trunk/bin/start-hbase.sh
* /hbase/trunk/bin/stop-hbase.sh
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Fix For: 0.96.0, 0.94.3
>
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455207#comment-13455207 ]
Lars Hofhansl commented on HBASE-6504:
--------------------------------------
should this be "head -n 1"? "head -1" works, but it is not document that way.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455227#comment-13455227 ]
Lars Hofhansl commented on HBASE-6504:
--------------------------------------
If head -1 is more portable, let's use that.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Drzal updated HBASE-6504:
---------------------------------
Status: Patch Available (was: Open)
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Michael Drzal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455993#comment-13455993 ]
Michael Drzal commented on HBASE-6504:
--------------------------------------
[~tsuna] does that work for you?
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6504) Adding GC details prevents HBase from
starting in non-distributed mode
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-6504:
---------------------------------
Fix Version/s: (was: 0.94.3)
0.94.2
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Fix For: 0.96.0, 0.94.2
>
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456370#comment-13456370 ]
Hudson commented on HBASE-6504:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #175 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/175/])
HBASE-6504 Adding GC details prevents HBase from starting in non-distributed mode (Revision 1385026)
Result = FAILURE
stack :
Files :
* /hbase/trunk/bin/rolling-restart.sh
* /hbase/trunk/bin/start-hbase.sh
* /hbase/trunk/bin/stop-hbase.sh
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Fix For: 0.96.0, 0.94.3
>
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Benoit Sigoure (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456124#comment-13456124 ]
Benoit Sigoure commented on HBASE-6504:
---------------------------------------
Yeah. One minor nit though: the form {{head -1}} is deprecated (and has been for years). Better to use {{head -n 1}}.
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6504) Adding GC details prevents HBase
from starting in non-distributed mode
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460747#comment-13460747 ]
Hudson commented on HBASE-6504:
-------------------------------
Integrated in HBase-0.94-security #53 (See [https://builds.apache.org/job/HBase-0.94-security/53/])
HBASE-6504 Adding GC details prevents HBase from starting in non-distributed mode (Revision 1385027)
Result = SUCCESS
stack :
Files :
* /hbase/branches/0.94/bin/rolling-restart.sh
* /hbase/branches/0.94/bin/start-hbase.sh
* /hbase/branches/0.94/bin/stop-hbase.sh
> Adding GC details prevents HBase from starting in non-distributed mode
> ----------------------------------------------------------------------
>
> Key: HBASE-6504
> URL: https://issues.apache.org/jira/browse/HBASE-6504
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Benoit Sigoure
> Assignee: Michael Drzal
> Priority: Trivial
> Labels: noob
> Fix For: 0.94.2, 0.96.0
>
> Attachments: HBASE-6504-output.txt, HBASE-6504.patch, HBASE-6504-v2.patch
>
>
> The {{conf/hbase-env.sh}} that ships with HBase contains a few commented out examples of variables that could be useful, such as adding {{-XX:+PrintGCDetails -XX:+PrintGCDateStamps}} to {{HBASE_OPTS}}. This has the annoying side effect that the JVM prints a summary of memory usage when it exits, and it does so on stdout:
> {code}
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed
> false
> Heap
> par new generation total 19136K, used 4908K [0x000000073a200000, 0x000000073b6c0000, 0x0000000751860000)
> eden space 17024K, 28% used [0x000000073a200000, 0x000000073a6cb0a8, 0x000000073b2a0000)
> from space 2112K, 0% used [0x000000073b2a0000, 0x000000073b2a0000, 0x000000073b4b0000)
> to space 2112K, 0% used [0x000000073b4b0000, 0x000000073b4b0000, 0x000000073b6c0000)
> concurrent mark-sweep generation total 63872K, used 0K [0x0000000751860000, 0x00000007556c0000, 0x00000007f5a00000)
> concurrent-mark-sweep perm gen total 21248K, used 6994K [0x00000007f5a00000, 0x00000007f6ec0000, 0x0000000800000000)
> $ ./bin/hbase org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed >/dev/null
> (nothing printed)
> {code}
> And this confuses {{bin/start-hbase.sh}} when it does
> {{distMode=`$bin/hbase --config "$HBASE_CONF_DIR" org.apache.hadoop.hbase.util.HBaseConfTool hbase.cluster.distributed`}}, because then the {{distMode}} variable is not just set to {{false}}, it also contains all this JVM spam.
> If you don't pay enough attention and realize that 3 processes are getting started (ZK, HM, RS) instead of just one (HM), then you end up with this confusing error message:
> {{Could not start ZK at requested port of 2181. ZK was started at port: 2182. Aborting as clients (e.g. shell) will not be able to find this ZK quorum.}}, which is even more puzzling because when you run {{netstat}} to see who owns that port, then you won't find any rogue process other than the one you just started.
> I'm wondering if the fix is not to just change the {{if [ "$distMode" == 'false' ]}} to a {{switch $distMode case (false*)}} type of test, to work around this annoying JVM misfeature that pollutes stdout.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira