Bug #10157
closed
PGLog::(read|write)_log don't write out rollback_info_trimmed_to
Added by Samuel Just over 9 years ago.
Updated about 9 years ago.
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.
- Status changed from New to 7
- Status changed from 7 to Pending Backport
- Backport set to giant,firefly
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?
- Status changed from Pending Backport to 7
- Status changed from 7 to Pending Backport
fea29b1 PGLog: include rollback_info_trimmed_to in (read|write)_log (in giant), c60da2f PGLog: include rollback_info_trimmed_to in (read|write)_log (in firefly),
- Status changed from Pending Backport to Resolved
Also available in: Atom
PDF