[jira] [Resolved] (ACCUMULO-3086) start-all.sh and stop-all.sh ignore the monitor configuration file

["Christopher Tubbs (JIRA)" <ji...@apache.org>]

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

Christopher Tubbs resolved ACCUMULO-3086.
-----------------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 1.6.3)
                       (was: 1.5.3)

After reviewing the implementation of the scripts, and the comments here, I think this is intended behavior (and I was able to confirm it applies to 1.7 and later versions at the time of this writing).

Like the "gc" file, the "monitor" file is singular (compared to the "masters", "slaves", and "tracers") because it is expected to only contain one. Further, the current behavior is for the monitor to get a lock in ZooKeeper, so the expectation is that only one is running (at least, for full functionality, like receiving the logs from other services). Also, the start-all.sh and stop-all.sh scripts do not ignore the monitor file. Rather, it is processed in the config.sh script, which is sourced by these scripts.

A workaround is described using start-server.sh to start an additional monitor.

I'm closing this since it is not a bug against these older versions, but intentional behavior. Please create a new issue if additional functionality is requested in the scripts/configuration in latest versions of Accumulo.

> start-all.sh and stop-all.sh ignore the monitor configuration file
> ------------------------------------------------------------------
>
>                 Key: ACCUMULO-3086
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3086
>             Project: Accumulo
>          Issue Type: Bug
>          Components: scripts
>    Affects Versions: 1.5.1, 1.6.0
>            Reporter: Craig W
>
> The start-all.sh script only starts a single monitor, ignoring the hosts listed in the $ACCUMULO_HOME/conf/monitor file. The same goes for stop-all.sh.
> As a workaround using "start-server.sh <host> monitor" for each monitor in the file works.
> The start-all and stop-all scripts should start and stop all monitors listed in the monitor configuration file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)