<div dir="ltr"><div>Is there a detailed explanation for resource monitor and start timeouts and intervals with examples, for dummies?</div><div><br></div><div>my resource configured s follows:<br></div>[root@lustre-mds1 ~]# pcs resource show MDT00<div>Warning: This command is deprecated and will be removed. Please use 'pcs resource config' instead.<br>Resource: MDT00 (class=ocf provider=heartbeat type=Filesystem)<br> Attributes: MDT00-instance_attributes<br> device=/dev/mapper/mds00<br> directory=/lustre/mds00<br> force_unmount=safe<br> fstype=lustre<br> Operations:<br> monitor: MDT00-monitor-interval-20s<br> interval=20s<br> timeout=40s<br> start: MDT00-start-interval-0s<br> interval=0s<br> timeout=60s<br> stop: MDT00-stop-interval-0s<br> interval=0s<br> timeout=60s<br></div><div><br></div><div>
<div>I issued manual failover with the following commands:</div><div></div>
</div><div>crm_resource --move -r MDT00 -H lustre-mds1</div><div><br></div><div>resource tried but returned back with the entries in pacemaker.log like these:</div><div>Dec 12 15:53:23 Filesystem(MDT00)[1886100]: INFO: Running start for /dev/mapper/mds00 on /lustre/mds00<br>Dec 12 15:53:45 Filesystem(MDT00)[1886100]: ERROR: Couldn't mount device [/dev/mapper/mds00] as /lustre/mds00</div><div><br></div><div>tried again with the same result:</div><div>Dec 12 16:11:04 Filesystem(MDT00)[1891333]: INFO: Running start for /dev/mapper/mds00 on /lustre/mds00<br>Dec 12 16:11:26 Filesystem(MDT00)[1891333]: ERROR: Couldn't mount device [/dev/mapper/mds00] as /lustre/mds00</div><div><br></div><div>Why it cannot move?<br></div><div><br></div><div>Does this 20 sec interval (between start and error) have anything to do with monitor interval settings?</div><div><br></div><div>[root@lustre-mgs ~]# pcs constraint show --full<br>Location Constraints:<br> Resource: MDT00<br> Enabled on:<br> Node: lustre-mds1 (score:100) (id:location-MDT00-lustre-mds1-100)<br> Node: lustre-mds2 (score:100) (id:location-MDT00-lustre-mds2-100)<br> Disabled on:<br> Node: lustre-mgs (score:-INFINITY) (id:location-MDT00-lustre-mgs--INFINITY)<br> Node: lustre1 (score:-INFINITY) (id:location-MDT00-lustre1--INFINITY)<br> Node: lustre2 (score:-INFINITY) (id:location-MDT00-lustre2--INFINITY)<br> Node: lustre3 (score:-INFINITY) (id:location-MDT00-lustre3--INFINITY)<br> Node: lustre4 (score:-INFINITY) (id:location-MDT00-lustre4--INFINITY)</div><div>Ordering Constraints:<br> start MGT then start MDT00 (kind:Optional) (id:order-MGT-MDT00-Optional)<br> start MDT00 then start OST1 (kind:Optional) (id:order-MDT00-OST1-Optional)<br> start MDT00 then start OST2 (kind:Optional) (id:order-MDT00-OST2-Optional)</div><div><br></div><div>with regards to ordering constraint: OST1 and OST2 are started now, while I'm exercising MDT00 failover.<br></div><div><br></div></div>