Fix : handle the case when rreq is nullptr at commit_ext

Author: yawzhang

conanfile.py

@@ -9,7 +9,7 @@
 
 class HomestoreConan(ConanFile):
     name = "homestore"
-    version = "7.0.8"
+    version = "7.0.9"
 
     homepage = "https://github.com/eBay/Homestore"
     description = "HomeStore Storage Engine"

src/lib/replication/repl_dev/raft_state_machine.cpp

@@ -205,7 +205,9 @@ raft_buf_ptr_t RaftStateMachine::commit_ext(nuraft::state_machine::ext_op_params
     int64_t lsn = s_cast< int64_t >(params.log_idx);
     repl_req_ptr_t rreq = lsn_to_req(lsn);
     if (m_rd.need_skip_processing(lsn)) {
-        RD_LOGI(rreq->traceID(), "Raft Channel: Log {} is expected to be handled by snapshot. Skipping commit.", lsn);
+        // If log replay is skipped, the rreq might be nullptr. Log the event with NO_TRACE_ID if rreq is null.
+        RD_LOGI(rreq == nullptr ? NO_TRACE_ID : std::to_string(rreq->traceID()),
+                "Raft Channel: Log {} is expected to be handled by snapshot. Skipping commit.", lsn);
         return m_success_ptr;
     }
     RD_DBG_ASSERT(rreq != nullptr, "Raft channel got null rreq for lsn={}", lsn);