Bug 1614526
| Summary: | MDS fails heartbeat timeout during create heavy workload | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Patrick Donnelly <pdonnell> |
| Component: | CephFS | Assignee: | Yan, Zheng <zyan> |
| Status: | CLOSED ERRATA | QA Contact: | Ramakrishnan Periyasamy <rperiyas> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.0 | CC: | ceph-eng-bugs, john.spray, mhackett, mmuir, pdonnell, rperiyas, tchandra, tserlin, zyan |
| Target Milestone: | z1 | ||
| Target Release: | 3.1 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.5-46.el7cp Ubuntu: ceph_12.2.5-31redhat1 | Doc Type: | No Doc Update |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-11-09 00:59:21 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: | |||
|
Comment 5
Yan, Zheng
2018-08-10 02:24:39 UTC
"handle_mds_beacon no longer laggy" message in above case can be explained by http://tracker.ceph.com/issues/23519 (In reply to Yan, Zheng from comment #6) > "handle_mds_beacon no longer laggy" message in above case can be explained > by http://tracker.ceph.com/issues/23519 Great catch! Thanks Zheng. As per comment 11, ran Automation regression runs and not observed failures. http://cistatus.ceph.redhat.com/ui/#cephci/launches/all%7Cpage.page=1&page.size=50&page.sort=start_time,number%2CDESC/5bc8bb4e36d1a000016d7470?page.page=1&page.size=50&page.sort=start_time%2CASC username: ceph, password: ceph Moving this bug to verified state. 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-2018:3530 |