Bug 1602165
| Summary: | [RFE] add configurable timeout to evict client that is not releasing caps | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Patrick Donnelly <pdonnell> |
| Component: | CephFS | Assignee: | Venky Shankar <vshankar> |
| Status: | CLOSED ERRATA | QA Contact: | Tejas <tchandra> |
| Severity: | low | Docs Contact: | Bara Ancincova <bancinco> |
| Priority: | high | ||
| Version: | 3.0 | CC: | ceph-eng-bugs, ceph-qe-bugs, hnallurv, kdreyer, vshankar |
| Target Milestone: | rc | Keywords: | FutureFeature |
| Target Release: | 3.2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.8-12.el7cp Ubuntu: ceph_12.2.8-10redhat1 | Doc Type: | Enhancement |
| Doc Text: |
.New option: `mds_cap_revoke_eviction_timeout`
This update adds a new configurable timeout for evicting clients that have not responded to capability revoke request by the Metadata Server (MDS). MDS can request clients to release its capabilities under certain conditions, such as another client requesting a capability that is currently held by a client. The client then releases its capabilities and acknowledges the MDS which can handover the capability to other clients. However, a misbehaving client might not acknowledge or could totally ignore the capability revoke request by the MDS, causing other clients to wait and thereby stalling requested I/O operations. Now, MDS can evict clients that have not responded to capability revoke requests for a configured timeout. This is disabled by default and can be enabled by setting the `mds_cap_revoke_eviction_timeout` configuration parameter.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-01-03 19:01: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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1629656 | ||
|
Description
Patrick Donnelly
2018-07-17 23:20:11 UTC
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. https://access.redhat.com/errata/RHBA-2019:0020 |