From: Venky Shankar Date: Mon, 6 Aug 2018 07:39:11 +0000 (-0400) Subject: doc: document cap revoke non-responders client eviction X-Git-Tag: v14.0.1~486^2~1 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=28a52d6fa14425fc877a69055dabe4e7c00f6b14;p=ceph.git doc: document cap revoke non-responders client eviction Fixes: http://tracker.ceph.com/issues/25188 Signed-off-by: Venky Shankar --- diff --git a/doc/cephfs/eviction.rst b/doc/cephfs/eviction.rst index 1da68fe33638..84e622ce64c9 100644 --- a/doc/cephfs/eviction.rst +++ b/doc/cephfs/eviction.rst @@ -21,12 +21,16 @@ libcephfs. Automatic client eviction ========================= -There are two situations in which a client may be evicted automatically: +There are three situations in which a client may be evicted automatically: On an active MDS daemon, if a client has not communicated with the MDS for over ``session_autoclose`` (a file system variable) seconds (300 seconds by default), then it will be evicted automatically. +On an active MDS daemon, if a client has not responded to cap revoke messages +for over ``mds_cap_revoke_eviction_timeout`` (configuration option) seconds. +This is disabled by default. + During MDS startup (including on failover), the MDS passes through a state called ``reconnect``. During this state, it waits for all the clients to connect to the new MDS daemon. If any clients fail to do