when replication is stopped $secs_behind is NULL, which causes an err…
…or in numeric comparisons
add logic to set a "writable" attribute as a counterpart for "readable"
NACK. This part has to go; it was in Yves' original draft and was thrown out. It's pointless; you don't need this attribute. You just tie your colo constraints to the Master role of the M/S set.
all righty... I'll have to find how to do that in the wonderfully clear and concise documentation, I guess :P
colocation c_writer_ip_on_master inf: p_ip ms_mysql:Master
... where p_ip is your "writer VIP" and ms_mysqlis your MySQL master/slave set.
This makes sense to me, I'd just prefer [ "$secs_behind" = "NULL" ] (with quotes). Or just do [ "$secs_behind" = "NULL" ] && secs_behind = 0, and then leave the comparison to $OCF_RESKEY_max_slave_lag as is.
[ "$secs_behind" = "NULL" ]
[ "$secs_behind" = "NULL" ] && secs_behind = 0
setting it to zero is not a good idea, you want infinity ;)
I'll just quote it (I actually stood on the fence a bit, but then I figured it should have a value at all times...)
Fair enough. :)
Revert e18c9ca, as it's been rejected
quote arguments in from the first comparison, just to b sure
I think there's no contest here. For once :) @m0n5t3r, it would be great if you could issue a new pull request, so that we don't have patch, patch back. Thanks!
can be closed as per #387