Skip to content

Commit e69e64b

Browse files
committed
chore: initializing already trigger elect automatically in leader_restart_clears_state
1 parent b107391 commit e69e64b

File tree

1 file changed

+2
-6
lines changed

1 file changed

+2
-6
lines changed

tests/tests/life_cycle/t50_leader_restart_clears_state.rs

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ async fn leader_restart_clears_state() -> anyhow::Result<()> {
3030
let mut router = RaftRouter::new(config.clone());
3131
router.enable_saving_committed = false;
3232

33-
let mut log_index = 0;
33+
let mut log_index;
3434

3535
// It must initialize a 3-nodes cluster so that it won't become leader in term-1, without election,
3636
// but instead, it becomes leader in term-2 after a round of election.
@@ -44,11 +44,7 @@ async fn leader_restart_clears_state() -> anyhow::Result<()> {
4444
tracing::info!("--- initialize node-0 wiht [0,1,2]");
4545
let n0 = router.get_raft_handle(&0)?;
4646
n0.initialize(btreemap! {0 => (), 1=>(), 2=>()}).await?;
47-
// log_index == 0;
48-
49-
tracing::info!("--- trigger election for node-0");
50-
n0.trigger().elect().await?;
51-
log_index += 1;
47+
log_index = 1; // 0 for initialization log, 1 for leader noop log
5248

5349
n0.wait(timeout()).state(ServerState::Leader, "node-0 should become leader").await?;
5450
n0.wait(timeout()).applied_index(Some(log_index), "node-0 applied log").await?;

0 commit comments

Comments
 (0)