提交 ab00790f 编写于 作者: H hf0 提交者: wangzelin.wzl

fix NOP log submit_timestamp fallback issue during reconfirm

上级 61ae7ea4
...@@ -832,6 +832,10 @@ int ObLogReconfirm::confirm_log_() ...@@ -832,6 +832,10 @@ int ObLogReconfirm::confirm_log_()
const uint64_t new_start_id = sw_->get_start_id(); const uint64_t new_start_id = sw_->get_start_id();
if (new_start_id > next_id_) { if (new_start_id > next_id_) {
next_id_ = new_start_id; next_id_ = new_start_id;
// When next_id_ is inceased, last_ts_ also need update
// Or later NOP log's submit_timestamp may fallback
const int64_t last_submit_ts = sw_->get_last_submit_timestamp();
(void)try_update_last_ts_(last_submit_ts);
CLOG_LOG(INFO, CLOG_LOG(INFO,
"there may execute a rebuild operation in\ "there may execute a rebuild operation in\
leader reconfirm", leader reconfirm",
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册