Return-Path: Delivered-To: apmail-hadoop-hbase-dev-archive@minotaur.apache.org Received: (qmail 48109 invoked from network); 11 Sep 2009 22:20:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 11 Sep 2009 22:20:27 -0000 Received: (qmail 99055 invoked by uid 500); 11 Sep 2009 22:20:26 -0000 Delivered-To: apmail-hadoop-hbase-dev-archive@hadoop.apache.org Received: (qmail 99017 invoked by uid 500); 11 Sep 2009 22:20:26 -0000 Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-dev@hadoop.apache.org Delivered-To: mailing list hbase-dev@hadoop.apache.org Received: (qmail 99007 invoked by uid 99); 11 Sep 2009 22:20:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Sep 2009 22:20:26 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Sep 2009 22:20:17 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id DBBF0234C498 for ; Fri, 11 Sep 2009 15:19:57 -0700 (PDT) Message-ID: <1283000307.1252707597898.JavaMail.jira@brutus> Date: Fri, 11 Sep 2009 15:19:57 -0700 (PDT) From: "stack (JIRA)" To: hbase-dev@hadoop.apache.org Subject: [jira] Resolved: (HBASE-1687) bin/hbase script doesn't allow for different memory settings for each daemon type In-Reply-To: <310811795.1248314354788.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HBASE-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-1687. -------------------------- Resolution: Fixed Hadoop Flags: [Reviewed] Committed to trunk and branch. Changed name of the regionserver variable from HBASE_RS_OPTS to be HBASE_REGIONSERVER_OPTS to be consistent. Also updated the metrics.xml doc. that gario recently contributed so it no longer describes adding above HBASE_*_OPTS.. no need now they have been committed. > bin/hbase script doesn't allow for different memory settings for each daemon type > --------------------------------------------------------------------------------- > > Key: HBASE-1687 > URL: https://issues.apache.org/jira/browse/HBASE-1687 > Project: Hadoop HBase > Issue Type: Bug > Reporter: Fernando > Fix For: 0.20.1 > > Attachments: hbase, HBASE-1687-ryan.patch, hbase-script.diff > > > bin/hbase assumes that all daemon types ( master, regionserver ), all use the same memory settings.. (HBASE_HEAPSIZE). > 1) I propose adding daemon specific OPTS much like hadoop already has ( HBASE_MASTER_OPTS, HBASE_REGIONSERVER_OPTS ). > So in bin/hbase, we would merge in the daemon specific opts within the case statement as such: > elif [ "$COMMAND" = "master" ] ; then > CLASS='org.apache.hadoop.hbase.master.HMaster' > HBASE_OPTS="$HBASE_OPTS $HBASE_MASTER_OPTS" > elif [ "$COMMAND" = "regionserver" ] ; then > CLASS='org.apache.hadoop.hbase.regionserver.HRegionServer' > HBASE_OPTS="$HBASE_OPTS $HBASE_REGIONSERVER_OPTS" > the new environment variables can then be added to hbase-env.sh as empty: > export HBASE_MASTER_OPTS="" > export HBASE_REGIONSERVER="" > ..etc > 2) I propose changes to that script to allow overriding the default memory ( HBASE_HEAPSIZE ), with daemon specific OPTS (HBASE_MASTER_OPTS, etc ). > Basically at the bottom of the bin/hbase script, it will check to see if the user has already set "-Xmx" in the HBASE_OPTS variable.. if so, then it will ignore the JAVA_HEAP_SIZE variable.. > as such: > # run it > if [[ $HBASE_OPTS == *-Xmx* ]]; then > exec "$JAVA" $HBASE_OPTS -classpath "$CLASSPATH" $CLASS "$@" > else > exec "$JAVA" $JAVA_HEAP_MAX $HBASE_OPTS -classpath "$CLASSPATH" $CLASS "$@" > fi > I will attach the file as I have modified it.. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.