Bug #22945: [journal] allocating a new tag after acquiring the lock should use on-disk committed position - rbd - Ceph

Actions

Copy link

Bug #22945

closed

[journal] allocating a new tag after acquiring the lock should use on-disk committed position

Added by Jason Dillaman about 6 years ago. Updated about 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Jason Dillaman

Target version:

% Done:

Source:

Tags:

Backport:

luminous,jewel

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

Related to issue #22932

If a client crashes before persisting its commit position and recovers, it will replay the on-disk events, advance the commit position, and allocate a new tag for future events. However, the tag predecessor is constructed using the original cached commit position and not the current commit position after replay.

Related issues 2 (0 open — 2 closed)