Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Sat, 14 Dec 2013 00:03:07 +0000 (UTC)
From: "Mike Drob (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12679497.1384551778207.35700.1386979387629@arcas>
In-Reply-To: <JIRA.12679497.1384551778207@arcas>
References: <JIRA.12679497.1384551778207@arcas>
Subject: [jira] [Commented] (ACCUMULO-1901) start-here.sh starts only one GC
 process even if more are defined
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/ACCUMULO-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848081#comment-13848081 ] 

Mike Drob commented on ACCUMULO-1901:
-------------------------------------

Working on cleaning up the code paths here, I'm seeking some confirmation - running all any of tracers, gc, and monitor should be completely optional, right?

> start-here.sh starts only one GC process even if more are defined
> -----------------------------------------------------------------
>
>                 Key: ACCUMULO-1901
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1901
>             Project: Accumulo
>          Issue Type: Bug
>          Components: gc, scripts
>    Affects Versions: 1.4.2, 1.4.3, 1.4.4, 1.5.0
>         Environment: Red Hat Enterprise Linux 6.3 64-bit
>            Reporter: Terry Porter
>            Assignee: Terry Porter
>            Priority: Minor
>              Labels: gc, newbie
>             Fix For: 1.4.5, 1.5.1, 1.6.0
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Even when a second host is listed in the gc file, the gc process is only ever started on the first host listed in the gc file.  The issue lies in lines 48-55 in start-here.sh as shown below:
> {code}
> for host in $HOSTS
> do
>     if [ ${host} = ${GC} ]
>     then
>         ${bin}/start-server.sh $GC gc "garbage collector"
>         break
>     fi
> done
> {code}
> Simple fix:
> {code}
> for host in $HOSTS
> do
>     if grep -q "^${host}\$" $ACCUMULO_HOME/conf/gc
>     then
>         ${bin}/start-server.sh ${host} gc "garbage collector"
>         break
>     fi
> done
> {code}
> This fix works in my 1.4.2 environment.  stop-here.sh already sweeps all possible processes to kill them, so I assumed no fix was needed there, but on my last cluster shutdown I found the stop-all.sh script only stopped the GC on the Master host. That fix is still outstanding.


--
This message was sent by Atlassian JIRA
(v6.1.4#6159)