-users] Re: How to force PG merging in one step?
Hi Frank,
> Is this not checked per OSD? This would be really bad, because if it
> just uses the average (currently 143.3) this warning will never be
> triggered in critical situations.
I believe you're right, I can only remember having
h-users@ceph.io
Subject: [ceph-users] Re: How to force PG merging in one step?
Hi Eugen.
During recovery there's another factor involved
(osd_max_pg_per_osd_hard_ratio), the default is 3. I had to deal with
that a few months back when I got inactive PGs due to many chunks and
"only" a
m S14
From: Frank Schilder
Sent: 12 October 2022 17:11:02
To: Eugen Block
Cc: ceph-users@ceph.io
Subject: [ceph-users] Re: How to force PG merging in one step?
Hi Eugen.
> During recovery there's another factor involved
> (osd_max_pg_per_osd_
Hi Eugen.
> During recovery there's another factor involved
> (osd_max_pg_per_osd_hard_ratio), the default is 3. I had to deal with
> that a few months back when I got inactive PGs due to many chunks and
> "only" a factor of 3. In that specific cluster I increased it to 5 and
> didn't encounte
s
Bygning 109, rum S14
________________
From: Eugen Block
Sent: 11 October 2022 14:13:45
To: ceph-users@ceph.io
Subject: [ceph-users] Re: How to force PG merging in one step?
Hi Frank,
I don't think it's the autoscaler interferring here but the default 5%
target_m
From: Eugen Block
Sent: 11 October 2022 14:13:45
To: ceph-users@ceph.io
Subject: [ceph-users] Re: How to force PG merging in one step?
Hi Frank,
I don't think it's the autoscaler interferring here but the default 5%
target_max_misplaced_ratio. I
Hi Frank,
I don't think it's the autoscaler interferring here but the default 5%
target_max_misplaced_ratio. I haven't tested the impacts of increasing
that to a much higher value, so be careful.
Regards,
Eugen
Zitat von Frank Schilder :
Hi all,
I need to reduce the number of PGs in a
