Project

General

Profile

Actions
Copy link

Bug #50004

closed

mon: Modify Paxos trim logic to be more efficient

Added by Aishwarya Mathuria about 3 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
pacific, octopus, nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rados
Component(RADOS):
Monitor
Pull request ID:
40168
Crash signature (v1):
Crash signature (v2):

Description

When the log ingest rate is higher than the trimming rate, monitors may end up consuming a lot of space and become unresponsive in the worst case. This is because currently the rate of trimming is bounded - maybe_trim() is called on every tick, where it trims "paxos_service_trim_max" at max.

The trimming logic needs to be smarter and change according to the log ingest rate.

Related issues 3 (0 open — 3 closed)

Copied to RADOS - Backport #50123: octopus: mon: Modify Paxos trim logic to be more efficient ResolvedNathan CutlerActions
Copied to RADOS - Backport #50124: pacific: mon: Modify Paxos trim logic to be more efficient Resolvedsinguliere _Actions
Copied to RADOS - Backport #50125: nautilus: mon: Modify Paxos trim logic to be more efficient ResolvedActions
Actions
Copy link

Also available in: Atom PDF