| Summary: | rpc: Lock frames should not be subjected to timeouts | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | krishnan parthasarathi <kparthas> |
| Component: | rpc | Assignee: | krishnan parthasarathi <kparthas> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | pre-release | CC: | nsathyan |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | --- | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Anand Avati
2011-09-23 10:11:35 UTC
Why? Locks that are blocked at the server can starve for time periods greater than the configured timeout and be granted later. In the current scheme of things, we would unwind the lock frame at the client end thereby resulting in a STALE/orphan lock at the server end. |