I’m surprised Pacemaker didn’t have any logging about unresolvable constraints. Even if the solver couldn’t figure out the particular constraints that broke the system, that would have been a great hint to avoid the WAL debugging, which turned out to be a bit of a non sequitur
At least at the time, we didn’t find anything useful in the logs. It’s possible that’s changed in later versions or would have been present with (e.g.) debug logging enabled.
There is a CLI tool for simulating specific situations in advance, but that requires foresight into edge cases that might happen, rather than telling you what it’s currently doing in production.
Lack of introspectability was ultimately a big reason we left Pacemaker behind and started using Stolon.
I’m surprised Pacemaker didn’t have any logging about unresolvable constraints. Even if the solver couldn’t figure out the particular constraints that broke the system, that would have been a great hint to avoid the WAL debugging, which turned out to be a bit of a non sequitur
At least at the time, we didn’t find anything useful in the logs. It’s possible that’s changed in later versions or would have been present with (e.g.) debug logging enabled.
There is a CLI tool for simulating specific situations in advance, but that requires foresight into edge cases that might happen, rather than telling you what it’s currently doing in production.
Lack of introspectability was ultimately a big reason we left Pacemaker behind and started using Stolon.