On Wed, 2017-10-04 at 10:59 -0700, Paolo Zarpellon wrote:
> Hi Ken,
> Indeed the migration-threshold was the problem :-(
>
> BTW, for a master-slave resource, is it possible to have different
> migration-thresholds?
> I.e. I'd like the slave to be restarted where it failed, but master
> to be
Hi Ken,
Indeed the migration-threshold was the problem :-(
BTW, for a master-slave resource, is it possible to have different
migration-thresholds?
I.e. I'd like the slave to be restarted where it failed, but master to be
migrated to the
other node right away (by promoting the slave there).
I've
On Mon, 2017-10-02 at 12:32 -0700, Paolo Zarpellon wrote:
> Hi,
> on a basic 2-node cluster, I have a master-slave resource where
> master runs on a node and slave on the other one. If I kill the slave
> resource, the resource status goes to "stopped".
> Similarly, if I kill the the master
Hi,
on a basic 2-node cluster, I have a master-slave resource where master runs
on a node and slave on the other one. If I kill the slave resource, the
resource status goes to "stopped".
Similarly, if I kill the the master resource, the slave one is promoted to
master but the failed one does not
