| Summary: | Test lock failover when making NFSv3 servers active/passive HA | |||
|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Perry Myers <pmyers> | |
| Component: | rgmanager | Assignee: | Dean Jansa <djansa> | |
| Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 5.6 | CC: | cluster-maint, cmarthal, djuran, edamato, syeghiay | |
| Target Milestone: | rc | Keywords: | TestOnly | |
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: |
Do not document.
|
Story Points: | --- | |
| Clone Of: | ||||
| : | 692221 (view as bug list) | Environment: | ||
| Last Closed: | 2012-02-21 06:19:08 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Do not document.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0163.html |
Description of problem: rgmanager supports making NFSv3 servers highly available in an active/passive manner when backed by a non-clustered filesystem. In this configuration scenario, you would want to be able to fail over the locks from one server to another so that the passive node can immediately pick up where the failed server left off. This lock failover has not been extensively tested in a while, so this bug is to track testing of lock failover specifically. Notes: > 1) Add this to /etc/sysconfig/nfs: > > STATDARG="-H /usr/sbin/clunfslock" > > 2) In cluster.conf, your service _MUST_ be structured like this; if you > don't get the dependency chains just right, it will not work: > > ... > <resources> > <nfsexport name="nfsexports"/> > </resources> > ... > <service name="foo" nfslock="1" ... > > <fs name="fs1" ... > > <nfsexport ref="nfsexports"> > <nfsclient ... /> > <nfsclient ... /> > ... > </nfsexport> > </fs> > <fs name="fs2" ... > > <nfsexport ref="nfsexports"> > <nfsclient ... /> > <nfsclient ... /> > ... > </nfsexport> > </fs> > <ip ... /> > </service>