Automatic client eviction
=========================
-There are three 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 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.
+#. 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
-so within the time window (``mds_reconnect_timeout``, 45 seconds by default)
-then they will be evicted.
+#. 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
+ so within the time window (``mds_reconnect_timeout``, 45 seconds by default)
+ then they will be evicted.
A warning message is sent to the cluster log if either of these situations
arises.