accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-2382) Using non-default CONTINUOUS_CONF_DIR breaks agitation
Date Thu, 20 Mar 2014 16:26:51 GMT

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

Sean Busbey resolved ACCUMULO-2382.
-----------------------------------

    Resolution: Fixed

> Using non-default CONTINUOUS_CONF_DIR breaks agitation
> ------------------------------------------------------
>
>                 Key: ACCUMULO-2382
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2382
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.5.1, 1.6.0
>         Environment: 1.5.1-rc2 on CDH 4.5.0
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>              Labels: newbie
>             Fix For: 1.5.2, 1.6.0
>
>         Attachments: ACCUMULO-2382.1-1.5.2-SNAPSHOT.patch.txt, ACCUMULO-2382.1-1.6.0-SNAPSHOT.patch.txt
>
>
> The start agitation script attempts to run the the various agitation scripts out of CONTINUOUS_CONF_DIR
rather than out of the installation directory.
> When CONTINUOUS_CONF_DIR points at configuration files outside of ACCUMULO_HOME/test/system/continuous,
the start agitation scripts are missing and agitation fails with a message to the stderr log
of the agitators. 
> All are similar to this example, given ACCUMULO_CONF_DIR=/etc/accumulo/continuous and
ACCUMULO_HOME=/usr/lib/accumulo-1.5.1-rc2, with start-agitator.sh run within /usr/lib/accumulo/1.5.1-rc2/test/system/continuous.
> {noformat}
> nohup: failed to run command `/etc/accumulo/continuous/master-agitator.pl': No such file
or directory
> {noformat}
> Workaround: Either don't use agitation, place configuration files in the default location,
or copy agitation perl scripts to CONTINUOUS_CONF_DIR



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message