Sometimes systemctl status command maybe delay, but never more than 3
seconds, so monitor timeout=100s can be thought enough?
And is monitor-still-in-progress-and-re-scheduling the reason for pacemaker
to stop an already active cinder service?
___
Manage
Did you notice any delay in 'systemctl status openstack-cinder-scheduler' ? As
far as I know the cluster will use systemd (or even maybe dbus) to get the info
of the service.
Also, 10s monitor intercal seems quite aggressive - have you considered
increasing that ?
Best Regards,Strahil Nikolov
On Sun, 2021-06-13 at 22:43 +0800, Acewind wrote:
> Dear guys,
> I'm using pacemaker-1.1.20 to construct an openstack HA system.
> After I stop&start the cluster, pcs monitor operation always be in
> progress for cinder-volume & cinder-scheduler service. But the
> systemd service is active and ope
The whole histroy operations:
I started systemd cinder-volume service resource manually on node host001,
then restart pcs cluster.
Pacemaker stops my cinder-volume service on host001, then cinder resources
are always shown stopped, never been started again.
于2021年6月14日周一 下午11:20写道：
> On Sun, 202
