[jira] Created: (HBASE-2217) VM OPTS for shell only

["stack (JIRA)" <ji...@apache.org>]

VM OPTS for shell only
----------------------

                 Key: HBASE-2217
                 URL: https://issues.apache.org/jira/browse/HBASE-2217
             Project: Hadoop HBase
          Issue Type: Improvement
            Reporter: stack


Over in hbase-2177 Ryan goes on how enabling gc logging, it shows on stdout when you fire the shell:

{code}
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.
{code}

Need to make an OPTS for the shell to use.... or do the above.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.