[
https://issues.apache.org/jira/browse/HBASE-2177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12832735#action_12832735
]
ryan rawson commented on HBASE-2177:
------------------------------------
so one problem with this is the irb then logs all GC to stdout, which is ugly.
I do something like this in my scripts:
export HBASE_OPTS=""
export HBASE_LOG_DIR=<somewhere>
export SERVER_GC_OPTS="$HBASE_OPTS -verbose:gc
-XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps -XX:+PrintGCDetails
-Xloggc:$HBASE_HOME/logs/gc-hbase.log"
export JMX_OPTS="-Dcom.sun.management.jmxremote.authenticate=true
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.password.file=$HBASE_HOME/conf/jmxremote.password
-Dcom.sun.management.jmxremote"
export HBASE_MASTER_OPTS="$SERVER_GC_OPTS
-Xloggc:$HBASE_LOG_DIR/logs/gc-master.log"
export HBASE_REGIONSERVER_OPTS="$SERVER_GC_OPTS
-Xloggc:$HBASE_LOG_DIR/gc-hbase.log -Dcom.sun.management.jmxremote.port=10102
$JMX_OPTS"
export HBASE_THRIFT_OPTS="-Xmx1000m $SERVER_GC_OPTS
-Xloggc:$HBASE_LOG_DIR/gc-hbase-thrift.log
-Dcom.sun.management.jmxremote.port=10103 $JMX_OPTS"
export HBASE_ZOOKEEPER_OPTS="-Xmx1000m $SERVER_GC_OPTS
-Xloggc:$HBASE_LOG_DIR/gc-zk.log -Dcom.sun.management.jmxremote.port=10104
$JMX_OPTS"
now you get remote JMX with logging to whatever directory (we have to log to
our large data partition since logs... can be big). Also the shell doesnt log
GC to stdout, and you can get separate GC logs for hmaster, hrs, thrift,
zookeeper.
> Add timestamping to gc logging options
> --------------------------------------
>
> Key: HBASE-2177
> URL: https://issues.apache.org/jira/browse/HBASE-2177
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
> Fix For: 0.20.4, 0.21.0
>
>
> http://forums.sun.com/thread.jspa?threadID=5165451
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
