tree d34fdb686e981915b7783676ff10664b65c037db
parent 82a831d26d8c3c45478240f77dab9cf1b4c9eb79
author Michael Blow <mblow@apache.org> 1477617320 -0400
committer Michael Blow <mblow@apache.org> 1477670478 -0700

Detect, Option to Forcibly Terminate AsterixDB Processes

Usability changes for sample local cluster:
1. Before start, check if there are any AsterixDB proceses running.  If so,
   error out.  This can be overridden with -f, which will proceed to start
   the cluster anyway.  This is useful in case where the other processes
   are operating on non-conflicting ports.
2. After stop, check if there are any AsterixDB processes running.  If
   so, emit a warning, and if -f is supplied to stop, kill any
   straggling processes.

Change-Id: Ie09c86fe67f7933574a03574fbe334e8c1be2bbd
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1316
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Michael Blow <mblow@apache.org>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Till Westmann <tillw@apache.org>