Looking at the date on this bug report, I think this was a trusty install; I tried to reproduce on xenial, and the last remaining unit went into state 'Initialized' not 'Disconnected'. When I then re-added another two units, they did correctly cluster with the remaining unit, and it did become the donor for the other two units.
I know there have been some improvements in this area between 5.5 -> 5.6, so this might be a much better story on xenial now.
That said, we probably should shutdown and purge pxc from any unit that is removed from a cluster; this is do-able via the 'stop' hook which is run on each unit as applications/services are destroyed.
Mario
Looking at the date on this bug report, I think this was a trusty install; I tried to reproduce on xenial, and the last remaining unit went into state 'Initialized' not 'Disconnected'. When I then re-added another two units, they did correctly cluster with the remaining unit, and it did become the donor for the other two units.
I know there have been some improvements in this area between 5.5 -> 5.6, so this might be a much better story on xenial now.
That said, we probably should shutdown and purge pxc from any unit that is removed from a cluster; this is do-able via the 'stop' hook which is run on each unit as applications/ services are destroyed.