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
On Wed, 4 Oct 2017, Jan Friesse wrote:
> > Could you clarify the formula for me? I don't see how "- 2" and "650"
> > map to this configuration.
>
> Since Corosync 2.3.4 when nodelist is used, totem.token is used only as
> a basis for calculating real token timeout. You can check corosync.conf
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
Jean,
Hi Jan,
On Tue, 3 Oct 2017, Jan Friesse wrote:
I hope this makes sense! :)
I would still have some questions :) but that is really not related to
the problem you have.
Questions are welcome! I am new to this stack, so there is certainly room
for learning and for improvement.
My
