[
https://issues.apache.org/jira/browse/ACCUMULO-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Vines updated ACCUMULO-792:
--------------------------------
Description:
The current start-up scripts use lists of hosts, and ssh to start and stop
processes. A better set of scripts would be installed with rpms/debs and would
start processes using /etc/init.
turn on the box, the processes start and wait for hadoop/zooekeeper (done)
turn on a master, and the system should go into ONLINE mode
Once this work is done, the ability to have rpms control the init.d and rc.d
levels comes naturally with future packaging work, either in Accumulo or BigTop
was:
The current start-up scripts use lists of hosts, and ssh to start and stop
processes. A better set of scripts would be installed with rpms/debs and would
start processes using /etc/init.
turn on the box, the processes start and wait for hadoop/zooekeeper (done)
turn on a master, and the system should go into ONLINE mode
rpms/debs turn on/off services if they are installed
relocatable, and perhaps installed multiple locations/user ids?
Some work has been done for debian, but needs to be done for RHEL based systems.
> Better scripts for start-up (RHEL)
> ----------------------------------
>
> Key: ACCUMULO-792
> URL: https://issues.apache.org/jira/browse/ACCUMULO-792
> Project: Accumulo
> Issue Type: New Feature
> Components: scripts
> Reporter: John Vines
> Assignee: John Vines
> Fix For: 1.5.0
>
>
> The current start-up scripts use lists of hosts, and ssh to start and stop
> processes. A better set of scripts would be installed with rpms/debs and
> would start processes using /etc/init.
> turn on the box, the processes start and wait for hadoop/zooekeeper (done)
> turn on a master, and the system should go into ONLINE mode
> Once this work is done, the ability to have rpms control the init.d and rc.d
> levels comes naturally with future packaging work, either in Accumulo or
> BigTop
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
