Files
ack-tegra/include/linux
Xiubo Li 4d7ace02ba ceph: fix mdsmap cluster available check based on laggy number
In case the max_mds > 1 in MDS cluster and there is no any standby
MDS and all the max_mds MDSs are in up:active state, if one of the
up:active MDSs is dead, the m->m_num_laggy in kclient will be 1.
Then the mount will fail without considering other healthy MDSs.

There manybe some MDSs still "in" the cluster but not in up:active
state, we will ignore them. Only when all the up:active MDSs in
the cluster are laggy will treat the cluster as not be available.

In case decreasing the max_mds, the cluster will not stop the extra
up:active MDSs immediately and there will be a latency. During it
the up:active MDS number will be larger than the max_mds, so later
the m_info memories will 100% be reallocated.

Here will pick out the up:active MDSs as the m_num_mds and allocate
the needed memories once.

Signed-off-by: Xiubo Li <xiubli@redhat.com>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
2020-01-27 16:53:39 +01:00
..
2019-11-12 11:43:29 -05:00
2019-10-31 16:54:00 +05:30
2019-11-15 23:44:48 +01:00
2019-11-26 10:26:26 +01:00
2019-10-09 19:33:43 -07:00
2019-12-03 11:20:37 +01:00
2019-12-08 12:42:19 +01:00
2019-12-09 10:36:44 -08:00
2019-11-20 09:40:10 +01:00
2019-12-01 12:59:06 -08:00
2019-10-02 06:36:50 -07:00
2019-10-04 12:31:46 -07:00
2019-10-15 13:34:25 +02:00
2019-11-11 09:02:56 +01:00
2019-12-04 19:44:14 -08:00
2019-12-09 10:36:44 -08:00
2019-12-25 17:08:33 -07:00
2019-10-15 20:40:06 -07:00
2019-11-14 19:06:47 -08:00
2019-11-06 08:55:23 -05:00
2019-10-09 12:06:19 -04:00
2019-11-06 08:55:23 -05:00
2019-11-13 19:09:47 +08:00
2019-12-06 10:47:28 +01:00
2019-10-19 22:55:46 +02:00
2019-11-14 13:07:48 +08:00
2019-10-10 14:55:24 -07:00
2019-12-01 06:29:17 -08:00
2019-11-13 12:15:34 -08:00
2020-01-02 16:15:33 -08:00
2019-11-13 00:33:21 +11:00
2019-11-07 07:00:26 +01:00
2019-11-14 12:20:02 +08:00
2020-01-17 22:33:37 -05:00