Hi, Ah, that seems to have fixed it. Hope it stays that way. I've raised it to 4 GB. Thanks to you both! Although I have to say that the message is IMHO *very* misleading: "1 MDSs report oversized cache" sounds to me like the cache is too large (i.e. wasting RAM unnecessarily). Shouldn't the message rather be "1 MDSs report *undersized* cache"? Weird. That's why I was wondering how small it should be to make Ceph happy but still be sufficient. If I had known that this message meant that the cache is too small, then I would have obviously just raised it until the message disappeared. Thanks again for your help! Much appreciated. BR Ranjan Am 05.12.19 um 16:47 schrieb Nathan Fish: > MDS cache size scales with the number of files recently opened by > clients. if you have RAM to spare, increase "mds cache memory limit". > I have raised mine from the default of 1GiB to 32GiB. My rough > estimate is 2.5kiB per inode in recent use. > > > On Thu, Dec 5, 2019 at 10:39 AM Ranjan Ghosh <ghosh@xxxxxx> wrote: >> Okay, now, after I settled the issue with the oneshot service thanks to >> the amazing help of Paul and Richard (thanks again!), I still wonder: >> >> What could I do about that MDS warning: >> >> === >> >> health: HEALTH_WARN >> >> 1 MDSs report oversized cache >> >> === >> >> If anybody has any ideas? I tried googling it, of course, but came up >> with no really relevant info on how to actually solve this. >> >> >> BR >> >> Ranjan >> >> >> _______________________________________________ >> ceph-users mailing list >> ceph-users@xxxxxxxxxxxxxx >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |