Bug 1657022 - mds session timeout cannot be modified
Summary: mds session timeout cannot be modified
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: CephFS
Version: 3.1
Hardware: All
OS: All
urgent
low
Target Milestone: z1
: 3.2
Assignee: Patrick Donnelly
QA Contact: Persona non grata
John Brier
URL:
Whiteboard:
Depends On:
Blocks: 1629656
TreeView+ depends on / blocked
 
Reported: 2018-12-06 20:54 UTC by Patrick Donnelly
Modified: 2019-03-07 15:51 UTC (History)
7 users (show)

Fixed In Version: RHEL: ceph-12.2.8-64.el7cp Ubuntu: ceph_12.2.8-49redhat1
Doc Type: Enhancement
Doc Text:
._session_timeout_ and _session_autoclose_ are now configurable by _ceph fs set_ You can now configure the `session_timeout` and `session_autoclose` options by using the `ceph fs set` command instead of setting them in the Ceph configuration file.
Clone Of:
Environment:
Last Closed: 2019-03-07 15:51:12 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 37540 0 None None None 2018-12-06 20:54:15 UTC
Red Hat Product Errata RHBA-2019:0475 0 None None None 2019-03-07 15:51:24 UTC

Description Patrick Donnelly 2018-12-06 20:54:15 UTC
Description of problem:

In Luminous, there are two configurations for setting the session timeout: (a) the MDSMap session_timeout field which is the ideal setting as it is seen by clients and (b) the mds_session_timeout config option. Currently, the MDS uses both but the MDSMap session_timeout controls the more important behavior of marking session stale.

Comment 16 errata-xmlrpc 2019-03-07 15:51:12 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:0475


Note You need to log in before you can comment on or make changes to this bug.