Is there any way I can unset pglog_hardlimit from osdmap?
I see the release note about this flag that it could not be unset but I
don't get why because the only diff when this flag is on is in timing pg
logs in aggressive mode and I don't get why if I unset this flag anything
might be hurt?
The way
Hello
I am running EC 8+2 setup on proxmox. Upgraded from octopus 15.2.11 to
pacific 16.2.4. Before upgrading the cluster was in a healthy state and all
2.449 PG's were active+clean.
After restarting all OSD's on pacific I have 23 PG's showing 1 unfound
object and 3 degraded objects each. I have
We have a ceph cluster with 408 osds, 3 mons and 3 rgws. We updated our
cluster from nautilus 14.2.14 to octopus 15.2.12 a few days ago. After
upgrading, the garbage collector process which is run after the lifecycle
process, causes slow ops and makes some osds to be restarted. In each
process the
I don't think it's a pool based config and in my cluster, it's set on
osdmap level flags. The pool I test in the higher latency cluster that has
much lower latency had 18 pgs and the higher latency pool has 8212 pgs.
The higher latency cluster has this flag the lower one doesn't have.
On Sun, Jul
Seena,
Which pool has the hardlimit flag set, the lower latency one, or the higher?
Brett
On Sun, Jul 18, 2021 at 12:17 PM Seena Fallah wrote:
> I've checked out my logs and see there is pg log trimming on each op and
> it's in aggressive mode. I checked the osdmap flags and see there is a
> p
I've checked out my logs and see there is pg log trimming on each op and
it's in aggressive mode. I checked the osdmap flags and see there is a
pglog_hardlimit flag set in it, but the other cluster doesn't have.
Should I tune any config related to this flag in v12.2.13?
I've seen this PR (https://g
