Could someone also explain the logics behind the decision to dump so much data
to the disk. Especially in container environments with resource limits this is
not really nice.
> -Original Message-
> Sent: Tuesday, 31 August 2021 19:16
> To: ceph-users@ceph.io
> Subject: [ceph-users] naut
: 31 August 2021 20:02:01
To: ceph-users@ceph.io
Subject: [ceph-users] Re: nautilus cluster down by loss of 2 mons
Could someone also explain the logics behind the decision to dump so much data
to the disk. Especially in container environments with resource limits this is
not really nice
During normal operation the size is under 1G. After the network ordeal
it was 65G. I gave the last mon all diskspace I could find under
/var/lib/ceph and started the mon again. it is now reaching 90G and
still growing
Does anyone have an idea howmuch disk free would be needed to get the
job d
Hi,
Maybe this is https://tracker.ceph.com/issues/50004 ?
14.2.22 and 15.2.13 have a more aggressive mon trimming to prevent
this sort of issue, when osds are spamming the mons with logs.
-- dan
On Tue, Aug 31, 2021 at 9:39 PM Marcel Kuiper wrote:
>
> During normal operation the size is under 1G.
