hcq/oceanbase
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

[BUG] set rec log ts to the on-goint log ts

Browse Source
This commit is contained in:
Handora
2022-11-14 12:05:40 +00:00
committed by wangzelin.wzl
parent a74951f7fb
commit 9abca6cd59
2 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
src/storage/tx/ob_trans_part_ctx.cpp
View File

@ -4846,11 +4846,16 @@ int ObPartTransCtx::refresh_rec_log_ts_()
prev_rec_log_ts_ = rec_log_ts_; prev_rec_log_ts_ = rec_log_ts_;
if (is_follower_()) { if (is_follower_()) {
// Case 1: As follower, the replay is in order, so we can simply reset it // Case 1: As follower, the replay is indead in order, while we cannot
// because all state changes in logs before max_durable_log_ts all // simply reset it because the replay is not atomic, and it may be in the
// successfully contained in this checkpoint and no new state changes // middle stage that the replay is currently on-going. So the necessary
// after max_durable_log_ts is contained in the checkpoint. // state before the log ts that is replaying may not be contained, so we
// need replay from the on-going log ts.
if (exec_info_.max_applied_log_ts_ != exec_info_.max_applying_log_ts_) {
rec_log_ts_ = exec_info_.max_applying_log_ts_;
} else {
rec_log_ts_ = OB_INVALID_TIMESTAMP; rec_log_ts_ = OB_INVALID_TIMESTAMP;
}
} else { } else {
// Case 2: As leader, the application is discrete and not in order, so we // Case 2: As leader, the application is discrete and not in order, so we
// rely on the first lo(we call it FCL later)g hasnot been applied as // rely on the first lo(we call it FCL later)g hasnot been applied as