-
Notifications
You must be signed in to change notification settings - Fork 912
Description
usage mode
I use the Block example. In the block example, the original data is written to a file. I write the original data to the storage engine.
Discovered problems
A data failed to be written to engine in 'on_apply()' function. The response was set to 'false'. Then Raft began to switch the Leader, but since it was 1 repliac, the switch failed. Finally, Raft exits. In the above situation, after the attempt to switch the leader fails, Raft should not exit, and the subsequent data should still be able to continue being written. If I want to achieve such a way, what should I do?
E0505 10:35:04.443906 449767 8589936136 /home/code/vector-search/raft_store/raft_store.cc:221] Fail to write to engine, msg:: Resource temporarily unavailable
E0505 10:35:04.443931 449767 8589936136 /home/code/vector-search/raft_store/raft_store.cc:336] Met raft error {type=StateMachineError, error_code=10002, error_text=StateMachine meet critical error when applying one or more tasks since index=2, none'} W0505 10:35:04.443946 449767 8589936136 /home/code/vector-search/third_party/braft/src/braft/node.cpp:1349] node test_db:test_space:0:102.0.0.15:8081:0:0 got error={type=StateMachineError, error_code=10002, error_text=StateMachine meet critical error when applying one or more tasks since index=2, none'}
I0505 10:35:04.443965 449767 8589936136 /home/code/vector-search/third_party/braft/src/braft/replicator.cpp:1516] Group test_db:test_space:0 Fail to find the next candidate
I0505 10:35:04.443987 449767 8589936136 /home/code/vector-search/raft_store/raft_store.cc:331] Node stepped down : Raft node(leader or candidate) is in error.