Bug #45903: BlueFS replay log grows without end - bluestore - Ceph

Actions

Bug #45903

closed

BlueFS replay log grows without end

Added by Adam Kupczyk almost 4 years ago. Updated about 3 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Target version:

Ceph - v12.2.12

% Done:

0%

Source:

Support

Tags:

Backport:

luminous,mimic,nautilus,octopus

Regression:

No

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

If data is slowly pouring to RocksDB WAL and new files are not created, BlueFS replay log can grow to the size that it no longer can be replayed.

Related issues 4 (0 open — 4 closed)

Actions

#1

Updated by Igor Fedotov almost 4 years ago

Seen that to. Looks like we're lacking some backports in luminous.
See https://github.com/ceph/ceph/pull/34876

Actions

#2

Updated by Neha Ojha almost 4 years ago

Status changed from New to Pending Backport
Backport set to luminous,mimic,nautilus,octopus
Pull request ID set to 35473

It will be good to get the fix into luminous and mimic for affected users.

Actions

#3

Updated by Nathan Cutler almost 4 years ago

Copied to Backport #46192: mimic: BlueFS replay log grows without end added

Actions

#4

Updated by Nathan Cutler almost 4 years ago

Copied to Backport #46193: octopus: BlueFS replay log grows without end added

Actions

#5

Updated by Nathan Cutler almost 4 years ago

Copied to Backport #46194: nautilus: BlueFS replay log grows without end added

Actions

#6

Updated by Nathan Cutler almost 4 years ago

Copied to Backport #46195: luminous: BlueFS replay log grows without end added

Actions

#7

Updated by Nathan Cutler about 3 years ago

Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions

Also available in: Atom PDF