[
https://issues.apache.org/jira/browse/ACCUMULO-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811544#comment-13811544
]
ASF subversion and git services commented on ACCUMULO-210:
----------------------------------------------------------
Commit 8f6f6701822edca9b04802497c7566be887d5448 in branch refs/heads/master
from [~ctubbsii]
[ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=8f6f670 ]
ACCUMULO-210 Make native it tests and rat check pass
> create packages that enable accumulo features on the given node
> ---------------------------------------------------------------
>
> Key: ACCUMULO-210
> URL: https://issues.apache.org/jira/browse/ACCUMULO-210
> Project: Accumulo
> Issue Type: Improvement
> Components: start
> Reporter: Eric Newton
> Assignee: Christopher Tubbs
> Priority: Critical
> Fix For: 1.6.0
>
>
> If you use the .rpm or .deb install packages, the base package is installed.
> If you try to run accumulo, you find it is not fully configured, and the
> start fails. There's no "slaves" file or "masters".... worse, the helpful
> start script tries to create single-node versions of these files. The
> package isn't very useful until this is done.
> We should layer packages to enable a node to run a given feature:
> tablet/logger, master, monitor, tracer. Installing the package will pull in
> the base package as a dependency and turn on the feature by installing a file
> somewhere. The start-here script should then read those features.
> I'm sure hadoop or hbase are doing something similar: at least investigate
> good practices.
> ese additional steps, basically writing some scripts that work from some
> configuration files in /etc, that would be nice.
> The goal is to do something like:
> {noformat}
> $ apt-get install accumulo-single-instance
> {noformat}
> Or
> {noformat}
> $ apt-get install accumulo-tserver accumulo-logger
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1#6144)
