Bug 1645693
| Summary: | [RFE] Improve default logging of MDS | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Ceph Storage | Reporter: | Mike Hackett <mhackett> |
| Component: | CephFS | Assignee: | Patrick Donnelly <pdonnell> |
| Status: | CLOSED ERRATA | QA Contact: | Persona non grata <nobody+410372> |
| Severity: | low | Docs Contact: | Aron Gunn <agunn> |
| Priority: | high | ||
| Version: | 3.2 | CC: | ceph-eng-bugs, edonnell, pasik, pdonnell, rperiyas, tchandra, tserlin |
| Target Milestone: | z1 | Keywords: | FutureFeature |
| Target Release: | 3.2 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | RHEL: ceph-12.2.8-71.el7cp Ubuntu: ceph_12.2.8-56redhat1 | Doc Type: | Enhancement |
| Doc Text: |
.Improved logging for Ceph MDS
Now, the Ceph MetaData Server (MDS) outputs more metrics concerning client sessions by default to the debug log. This includes the creation of the client session and other metadata. This information is useful for storage administrators to see when a new client session is created and how long it took to establish a connection.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-03-07 15:50:56 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
Mike Hackett
2018-11-02 21:15:59 UTC
The new session log information is at "debug_mds=2" level. Once a client connects, you should be able to see a message like:
> 2018-12-17 17:21:31.682 7f822703c700 2 mds.0.server New client session: addr="127.0.0.1:60552/2307908923",elapsed=0.013384,throttled=0.000071,status="ACCEPTED",root="/"
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:0475 |