Bug 2143459
| Summary: | Integrate the latest sanlock to RHEL | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | rainzhang2 <rain.zhang> |
| Component: | sanlock | Assignee: | David Teigland <teigland> |
| Status: | CLOSED MIGRATED | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | low | ||
| Version: | 9.3 | CC: | agk, cluster-maint |
| Target Milestone: | rc | Keywords: | MigratedToJIRA, Triaged |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-23 18:48:24 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
rainzhang2
2022-11-17 01:51:19 UTC
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. Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |