You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2013/12/04 20:20:36 UTC
[jira] [Comment Edited] (ACCUMULO-1901) start-here.sh starts only
one GC process even if more are defined
[ https://issues.apache.org/jira/browse/ACCUMULO-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839239#comment-13839239 ]
Josh Elser edited comment on ACCUMULO-1901 at 12/4/13 7:19 PM:
---------------------------------------------------------------
What happens when you have no gc file? No gc process? Use the master instead?
To be honest, I never realized that the gc file was optional.
was (Author: elserj):
What happens when you have no gc file? No gc process? Use the master instead?
> 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#6144)