Closed GoogleCodeExporter closed 8 years ago
BTW, shutdown seems to "work" but not really if you haven't stopped your
instance?
shutdown stops the Managix' zookeeper service which has no impact on a running
Asterix instance. One may shutdown managix but continue to work with an Asterix
instance as long as one does not need to perform any management task. At this
point managix service is not running and it doesn't need to.
In the event when user wants to execute a management task, Managix command will
auto-start its backend service (zookeeper) if its not already running. This is
useful across system/laptop restarts so that Managix service starts only on
"demand" and is done implicitly without troubling the user.
Original comment by ram...@uci.edu
on 20 Jul 2013 at 3:09
Shutdown command is useful only when user knows s/he wont be running any
management tasks and doesn;t need to have any managix process running in
background and occupying resources/ports. Shutdown work but the implicit
restart of the managix service upon executing a mgmt task makes it appear that
shutdown did not do its job.
please suggest is we need a change here.
Original comment by RamanGro...@gmail.com
on 20 Jul 2013 at 3:23
Okay - got it - the re-spinning is still needed to clarify what managix "is" -
and its relationship to running instances (the lifecycle
confusion/clarification above) should be spelled out too. Thx!
Original comment by dtab...@gmail.com
on 20 Jul 2013 at 5:20
PS - I don't think any change in managix itself is needed, shutdown-wise - just
a clarification of its relationship to (multiple) running instances and what
its commands do (and don't do). What it does seems quite reasonable, it's just
not what I was thinking it was doing. :-)
Original comment by dtab...@gmail.com
on 20 Jul 2013 at 5:22
added as part of FAQ the sequence of steps required to upgrade an Asterix
instance
Original comment by RamanGro...@gmail.com
on 20 Sep 2013 at 5:35
Original issue reported on code.google.com by
dtab...@gmail.com
on 19 Jul 2013 at 9:09