adonis0147 opened a new issue, #24994:
URL: https://github.com/apache/doris/issues/24994

   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/doris/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Version
   
   Version: 0.15.5
   
   ### What's Wrong?
   
   After rebooting the MASTER FE, the FE cluster is down and all FE nodes can't 
start successfully.
   
   ```shell
   # FE 1
   2023-09-26 21:53:18,502 INFO (leaderCheckpointer|198) 
[Catalog.replayJournal():2495] replayed journal id is 819177628, replay to 
journal id is 819221799
   2023-09-26 21:53:18,502 ERROR (leaderCheckpointer|198) 
[BDBJournalCursor.<init>():84] Can not find the key:819177629, fail to get 
journal cursor. will exit.
   
   # FE 2
   2023-09-26 21:52:49,498 INFO (leaderCheckpointer|154) 
[Catalog.replayJournal():2495] replayed journal id is 819177628, replay to 
journal id is 819221581
   2023-09-26 21:52:49,498 ERROR (leaderCheckpointer|154) 
[BDBJournalCursor.<init>():84] Can not find the key:819177629, fail to get 
journal cursor. will exit.
   
   # FE 3
   2023-09-26 21:54:08,687 ERROR (stateListener|73) 
[Catalog.transferToMaster():1214] fencing failed. will exit.
   ```
   
   ### What You Expected?
   
   All FE start successfully.
   
   ### How to Reproduce?
   
   This issue was spot in our production environment.
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to