accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Terry Porter (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-1901) start-here.sh starts only one GC process even if more are defined
Date Tue, 19 Nov 2013 05:01:23 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Terry Porter updated ACCUMULO-1901:
-----------------------------------

    Labels: gc newbie  (was: newbie)
    Status: Patch Available  (was: Open)

Corrects start-here.sh to spin up multiple GCs if defined. Still need to resolve shutdown
issue, as stop-all.sh seems to only stop the GC on the master host.

> 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.5.0, 1.4.4, 1.4.3, 1.4.2
>         Environment: Red Hat Enterprise Linux 6.3 64-bit
>            Reporter: Terry Porter
>            Priority: Minor
>              Labels: newbie, gc
>             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 no fix needed there.
> I posted the fix in case anyone needs this ASAP as this will be my first development
work with an open source project, but I hope to be able to post the fix this weekend.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message