[jira] [Commented] (HBASE-14360) Client GC log path is not computed
[
https://issues.apache.org/jira/browse/HBASE-14360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14876310#comment-14876310
]
Nick Dimiduk commented on HBASE-14360:
--
So I applied the patch, uncommented a line in hbase-env.sh, and i'm seeing a
file named {{.0}} in {{$(pwd)}}.
{noformat}
$ git diff conf/hbase-env.sh
diff --git a/conf/hbase-env.sh b/conf/hbase-env.sh
index b7d00d1..21a45dc 100644
--- a/conf/hbase-env.sh
+++ b/conf/hbase-env.sh
@@ -70,7 +70,7 @@ export HBASE_REGIONSERVER_OPTS="$HBASE_REGIONSERVER_OPTS
-XX:PermSize=128m -XX:M
# This enables basic GC logging to its own file with automatic log rolling.
Only applies to jdk 1.6.0_34+ and 1.7.0_2+.
# If FILE-PATH is not replaced, the log file(.gc) would still be generated in
the HBASE_LOG_DIR .
-# export CLIENT_GC_OPTS="-verbose:gc -XX:+PrintGCDetails
-XX:+PrintGCDateStamps -Xloggc: -XX:+UseGCLogFileRotation
-XX:NumberOfGCLogFiles=1 -XX:GCLogFileSize=512M"
+export CLIENT_GC_OPTS="-verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps
-Xloggc: -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=1
-XX:GCLogFileSize=512M"
# See the package documentation for org.apache.hadoop.hbase.io.hfile for other
configurations
# needed setting up off-heap block caching.
{noformat}
The client I'm using is {{ltt}} via hbase shell, so {{./bin/hbase ltt
-data_block_encoding FAST_DIFF -bloom ROWCOL -num_keys 10 -read 50 -write
10:1000}}.
> Client GC log path is not computed
> --
>
> Key: HBASE-14360
> URL: https://issues.apache.org/jira/browse/HBASE-14360
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Reporter: Nick Dimiduk
>Assignee: Gabor Liptak
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-14360.1.patch
>
>
> Looking for GC logs on the client side, I noticed the nice work from
> HBASE-7817 that gives us the settings, just uncomment and run. Giving this a
> try with ltt, looks like {{}} is not replaced according to the
> comments. Seems this work is done by {{bin/hbase-daemon.sh}}, not
> {{bin/hbase}}. The result is my ltt produced a file {{.0}} in
> {{$(pwd)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14360) Client GC log path is not computed
[
https://issues.apache.org/jira/browse/HBASE-14360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742132#comment-14742132
]
Gabor Liptak commented on HBASE-14360:
--
[~ndimiduk] Could you please validate? Thanks
> Client GC log path is not computed
> --
>
> Key: HBASE-14360
> URL: https://issues.apache.org/jira/browse/HBASE-14360
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Reporter: Nick Dimiduk
>Assignee: Gabor Liptak
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-14360.1.patch
>
>
> Looking for GC logs on the client side, I noticed the nice work from
> HBASE-7817 that gives us the settings, just uncomment and run. Giving this a
> try with ltt, looks like {{}} is not replaced according to the
> comments. Seems this work is done by {{bin/hbase-daemon.sh}}, not
> {{bin/hbase}}. The result is my ltt produced a file {{.0}} in
> {{$(pwd)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (HBASE-14360) Client GC log path is not computed
[
https://issues.apache.org/jira/browse/HBASE-14360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14734069#comment-14734069
]
Hadoop QA commented on HBASE-14360:
---
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12754539/HBASE-14360.1.patch
against master branch at commit e95358a7fc3f554dcbb351c8b7295cafc01e8c23.
ATTACHMENT ID: 12754539
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+0 tests included{color}. The patch appears to be a
documentation, build,
or dev-support patch that doesn't require tests.
{color:green}+1 hadoop versions{color}. The patch compiles with all
supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0 2.7.1)
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 protoc{color}. The applied patch does not increase the
total number of protoc compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 checkstyle{color}. The applied patch does not increase the
total number of checkstyle errors
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 2.0.3) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 lineLengths{color}. The patch does not introduce lines
longer than 100
{color:green}+1 site{color}. The mvn post-site goal succeeds with this patch.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/PreCommit-HBASE-Build/15456//testReport/
Release Findbugs (version 2.0.3)warnings:
https://builds.apache.org/job/PreCommit-HBASE-Build/15456//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors:
https://builds.apache.org/job/PreCommit-HBASE-Build/15456//artifact/patchprocess/checkstyle-aggregate.html
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/15456//console
This message is automatically generated.
> Client GC log path is not computed
> --
>
> Key: HBASE-14360
> URL: https://issues.apache.org/jira/browse/HBASE-14360
> Project: HBase
> Issue Type: Bug
> Components: scripts
>Reporter: Nick Dimiduk
>Assignee: Gabor Liptak
>Priority: Minor
> Labels: beginner
> Attachments: HBASE-14360.1.patch
>
>
> Looking for GC logs on the client side, I noticed the nice work from
> HBASE-7817 that gives us the settings, just uncomment and run. Giving this a
> try with ltt, looks like {{}} is not replaced according to the
> comments. Seems this work is done by {{bin/hbase-daemon.sh}}, not
> {{bin/hbase}}. The result is my ltt produced a file {{.0}} in
> {{$(pwd)}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
