Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0D23411C99 for ; Thu, 17 Jul 2014 02:42:05 +0000 (UTC) Received: (qmail 51985 invoked by uid 500); 17 Jul 2014 02:42:04 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 51937 invoked by uid 500); 17 Jul 2014 02:42:04 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 51925 invoked by uid 99); 17 Jul 2014 02:42:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2014 02:42:04 +0000 Date: Thu, 17 Jul 2014 02:42:04 +0000 (UTC) From: "Hudson (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-2217) VM OPTS for shell only MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-2217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14064505#comment-14064505 ] Hudson commented on HBASE-2217: ------------------------------- FAILURE: Integrated in HBase-0.94-JDK7 #155 (See [https://builds.apache.org/job/HBase-0.94-JDK7/155/]) HBASE-2217 VM OPTS for shell only (apurtell: rev 225561cc6d6f69fe948b908bb305a73faab9c336) * bin/hbase > VM OPTS for shell only > ---------------------- > > Key: HBASE-2217 > URL: https://issues.apache.org/jira/browse/HBASE-2217 > Project: HBase > Issue Type: Improvement > Reporter: stack > Assignee: Andrew Purtell > Fix For: 0.99.0, 0.96.3, 0.98.5, 0.94.22, 2.0.0 > > Attachments: HBASE-2217.patch > > > 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= > 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 was sent by Atlassian JIRA (v6.2#6252)