As a follow up, our MDS was locking up under load so I went ahead and tried
it. It seemed that some directories were getting bounced around the MDS
servers and load would transition from one to the other. Initially my guess
was that some of these old clients were sending all requests to one MDS
On Sat, May 2, 2020 at 3:12 PM Robert LeBlanc wrote:
>
> If there was a network blip and a client was having trouble reconnecting, do
> you think reducing the ranks to 1 would allow them to connect? At which point
> the ranks could be increased again.
>
> Or is it a matter of the client kernel
If there was a network blip and a client was having trouble reconnecting,
do you think reducing the ranks to 1 would allow them to connect? At which
point the ranks could be increased again.
Or is it a matter of the client kernel panicking so any kind of
reconnection won't work?
Thanks
Thanks guys. We are so close to the edge that we may just take that chance,
usually the only reason an active client has to reconnect is because we
have to bounce the MDS because it's overwhelmed.
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
I've seen issues with clients reconnects on older kernels, yeah. They
sometimes get stuck after a network failure
Paul
--
Paul Emmerich
Looking for help with your Ceph cluster? Contact us at https://croit.io
croit GmbH
Freseniusstr. 31h
81247 München
www.croit.io
Tel: +49 89 1896585 90
On
On Tue, Apr 28, 2020 at 11:52 AM Robert LeBlanc wrote:
>
> In the Nautilus manual it recommends >= 4.14 kernel for multiple active
> MDSes. What are the potential issues for running the 4.4 kernel with
> multiple MDSes? We are in the process of upgrading the clients, but at
> times overrun the
