Hello On Wed, Feb 4, 2015 at 2:20 AM, Stuart Bishop <[email protected]> wrote: > On 3 February 2015 at 21:23, Stuart Bishop <[email protected]> > wrote: >> On 28 January 2015 at 21:03, Mario Splivalo > [... snip ] > > While typing up https://bugs.launchpad.net/juju-core/+bug/1417874 I > realized that your proposed solution of a pre-departure hook is the > only one that can work. Once -departed hooks start firing both the > doomed unit and the leader have already lost the access needed to > decommission the departing node.
I have been struggling the last hours with the same exact issue trying to add replication to memcached. The problem is that there is no a point on which i can identify what's the exact departing unit? And this leads to manual operator intervention, which is _highly_ non desirable for a juju deployed environment. +1 for having this feature implemented. -- Jorge Niedbalski R. Software Sustaining Engineer CTS - Engineering Team gpg:0x3DA28544, irc: niedbalski -- Juju-dev mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju-dev
