stop hook does not fire when units removed from service

Bug #872264 reported by James Page on 2011-10-11
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
juju-core
High
William Reade
pyjuju
High
Unassigned

Bug Description

Scenario:

Cassandra charm deployed with 4 units supporting the service. Ring is balanced automatically over the four units.

Action:

One or more service units are removed using juju remove-unit from the cassandra service.

Result:

With providers where the underlying machine is not instantly terminated, the removed units remain in the cassandra ring as cassandra is still running on the units.

Ideally the charm should be able to cope with the following actions:

1) Controlled (juju remove-unit) -> unit removes itself from the ring, purges its local data store and shuts down. In this case the data on the node is streamed from the node itself.
2) Uncontrolled (unit goes AWOL) -> the remaining units in the cluster need to detect this and complete a removal on the node from the ring - ideally through some sort of 'run once per deployed service, not unit' hook. In this case the data is streamed from remaining replicas of the data on the unit that has gone awol.

Changed in juju:
milestone: none → florence
Kapil Thangavelu (hazmat) wrote :

attached IRC Conversation log around the issue

Changed in juju:
status: New → Confirmed
importance: Undecided → High
Changed in juju:
importance: High → Critical
Jim Baker (jimbaker) on 2012-02-15
Changed in juju:
assignee: nobody → Jim Baker (jimbaker)
status: Confirmed → In Progress
Kapil Thangavelu (hazmat) wrote :

This needs a spec and some discussion, i've got some notes in draft spec form here lp:~hazmat/juju/unit-stop

Jim Baker (jimbaker) on 2012-02-15
Changed in juju:
status: In Progress → Confirmed
assignee: Jim Baker (jimbaker) → nobody
Kapil Thangavelu (hazmat) wrote :

after talking over with a few folks, it seems this one isn't really critical for the release.. pushing it to the next milestone

Changed in juju:
importance: Critical → High
milestone: florence → galapagos
Changed in juju:
milestone: galapagos → honolulu
Mark Mims (mark-mims) wrote :

This is noticed from 'destroy-service' as well.

Changed in juju:
milestone: 0.6 → 0.7
Changed in juju-core:
status: New → Confirmed
importance: Undecided → High
William Reade (fwereade) on 2012-10-25
Changed in juju-core:
assignee: nobody → William Reade (fwereade)
status: Confirmed → Fix Released
tags: added: goju-resolved
Changed in juju:
milestone: 0.7 → 0.8
Curtis Hovey (sinzui) on 2013-10-12
Changed in juju:
status: Confirmed → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers