GenerousMan commented on issue #7477:
URL: https://github.com/apache/rocketmq/issues/7477#issuecomment-1782616428

   Hello, I have verified the situation you mentioned. Below are some of my 
testing processes.
   
   ### Verification process
   
![image](https://github.com/apache/rocketmq/assets/21073949/76845777-596a-4179-b6c1-f657544c5162)
   
   Send a message and save the sending status of one of the messages:
   SendResult [sendStatus=SEND_OK, msgId=AC1004C454E75D099F62895F43C403E7, 
offsetMsgId=AC1004C4000078D300000000001181B9, messageQueue=MessageQueue 
[topic=TopicTest, brokerName=RaftNode00, queueId=1], queueOffset=999]
   
   Close using the test script and restart.
   
![image](https://github.com/apache/rocketmq/assets/21073949/e8661483-fad3-4a03-a40e-5e5e4a2cd8cc)
   
   Still able to query:
   
![image](https://github.com/apache/rocketmq/assets/21073949/359b42cd-c697-4236-8a1c-d56e2f48e322)
   
   Forcefully kill the process after startup and observe the query result:
   
![image](https://github.com/apache/rocketmq/assets/21073949/91e0ab03-155c-4ab6-a2a7-ee3f1ac9a1de)
   
![image](https://github.com/apache/rocketmq/assets/21073949/b512a26f-da93-41b1-8898-157fbfaf81ff)
   
   ### Preliminary conclusion
   After killing the broker with kill -9, it is indeed possible that the msgId 
cannot be found. The index folder is emptied after restarting, indicating that 
the recover process cleans up the index files.
   
![image](https://github.com/apache/rocketmq/assets/21073949/46563582-008c-4f73-94fc-aee6fe19d414)
   
   However, the offsetId can still be found, indicating that the message is not 
lost and is still in the commit log.
   Further investigation is needed to determine the specific cause.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to