Re: [ClusterLabs] restarting pacemakerd

2016-06-18 Thread Dimitri Maziuk
On 06/18/2016 02:15 PM, Digimer wrote: > When your focus is availability, restarting makes sense. What you want > to do is alert an admin that a restart was needed, so that he or she can > investigate the cause. Pacemaker 1.1.15 allows for this alerting now. When your focus is availability,

Re: [ClusterLabs] restarting pacemakerd

2016-06-18 Thread Digimer
On 18/06/16 03:04 PM, Dmitri Maziuk wrote: > On 2016-06-18 05:15, Ferenc Wágner wrote: > ... >> On the other hand, one could argue that restarting failed services >> should be the default behavior of systemd (or any init system). Still, >> it is not. > > As an off-topic snide comment, I never

Re: [ClusterLabs] restarting pacemakerd

2016-06-18 Thread Dmitri Maziuk
On 2016-06-18 05:15, Ferenc Wágner wrote: ... On the other hand, one could argue that restarting failed services should be the default behavior of systemd (or any init system). Still, it is not. As an off-topic snide comment, I never understood the thinking behind that: restarting without

[ClusterLabs] restarting pacemakerd

2016-06-18 Thread Ferenc Wágner
Hi, Could somebody please elaborate a little why the pacemaker systemd service file contains "Restart=on-failure"? I mean that a failed node gets fenced anyway, so most of the time this would be a futile effort. On the other hand, one could argue that restarting failed services should be the