Actions
Bug #10157
closedPGLog::(read|write)_log don't write out rollback_info_trimmed_to
% Done:
0%
Source:
other
Tags:
Backport:
giant,firefly
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
In practice, this means that replicated pgs will scan their log on the first operations after boot needlessly. EC pgs will tend to send an unnecessary transaction with the first operation after boot.
Updated by Samuel Just over 9 years ago
- Status changed from 7 to Pending Backport
- Backport set to giant,firefly
Updated by Dong Lei over 9 years ago
Hi sam:
"EC pgs will tend to send an unnecessary transaction with the first operation after boot."
This unnecessary transaction is supposed to be very big if the log tail is far away from the last rollback_info_trimmed_to(before reboot), right?
Updated by Samuel Just about 9 years ago
- Status changed from Pending Backport to 7
Updated by Samuel Just about 9 years ago
- Status changed from 7 to Pending Backport
Updated by Loïc Dachary about 9 years ago
- giant backport fea29b1bcbd17b3d1f642398ec70dbe258bbc98f
Updated by Loïc Dachary about 9 years ago
Updated by Loïc Dachary about 9 years ago
- Status changed from Pending Backport to Resolved
Actions