Description of problem: sanlock has an important enhancement to make the watchdog timeout configurable, please integrate into RHEL. https://pagure.io/sanlock/c/748e8325fd0b2e09469c76f584b8e08c1ef03ca6?branch=master Background: https://pagure.io/sanlock/issue/7 Version-Release number of selected component (if applicable): Current version: sanlock-lib-3.8.4-3 How reproducible: Please refer to https://pagure.io/sanlock/issue/7 Actual results: watchdog_fire_timeout is hardcoded to 60 seconds. Expected results: watchdog_fire_timeout is configurable. Additional info:
Can you please describe the use case you have for sanlock? What other software would use sanlock with this configuration? sanlock features are often tested and supported as a component of a larger product.
Hi, We use sanlock+lvmlockd for shared VG. We have a 2 nodes Active/Standby HA system with shared storage, only one node can access the shared storage at the same time. So, we use shared VG with sanlock+lvmlockd, then only one node can activate VG at the same time. In case active node is failed, the standby node should activate VG and take over active role. As current sanlock timer, standby node can not activate VG until the following time passed: 8 * io_timeout_seconds + watchdog_fire_timeout(hardcode 60 seconds) To decrease the wait time, we need watchdog_fire_timeout to be confiruable.
Thanks for the information, we will need to test lvmlockd with the new sanlock timeout settings. Most new features like this would be added only to RHEL9; very few changes are now added to RHEL8. You will notice in the commit above that a lower watchdog_fire_timeout should be combined with a shorter io_timeout, e.g. watchdog_fire_timeout=30 and io_timeout=5. You should also verify that the smaller io_timeout works well with your storage system. Smaller io_timeouts can trigger unnecessary failures when the i/o response from the storage is slow.