Hi Xiubo.
... I am more interested in the kclient side logs.
Just want to
know why that oldest request got stuck so long.
I'm afraid I'm a bad admin in this case. I don't have logs from the host any
more, I would have needed the output of dmesg and this is gone. In case it happens again I
will try to pull the info out.
The tracker
https://tracker.ceph.com/issues/22885 sounds a lot more violent than our
situation. We had no problems with the MDSes, the cache didn't grow and the relevant
one was also not put into read-only mode. It was just this warning showing all the time,
health was OK otherwise. I think the warning was there for at least 16h before I failed
the MDS.
The MDS log contains nothing, this is the only line mentioning this client:
2023-07-20T00:22:05.518+0200 7fe13df59700 0 log_channel(cluster) log [WRN] :
client.145678382 does not advance its oldest_client_tid (16121616), 100000 completed
requests recorded in session
Best regards,
=================
Frank Schilder
AIT Risø Campus
Bygning 109, rum S14