[KUDU-2976] MoveTabletParamTest.Test is flaky

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Component/s: test
• Assignee: Unassigned
• Reporter: Alexey Serbin
• Created: 16/Oct/19 18:11
• Updated: 16/Oct/19 18:11

Description

The test in EnableKudu1097AndDownTS/MoveTabletParamTest.Test/0 configuration sometime fails with the following error message:

src/kudu/tools/kudu-admin-test.cc:390: Failure
Value of: s.ok()
  Actual: false
Expected: true
Runtime error: kudu: process exited with non-zero status
 1
stdout: 
stderr: W1016 04:31:50.112155  2734 flags.cc:404] Enabled unsafe flag: --never_fsync=true
Illegal state: Leader has not yet committed an operation in its own term

To fix, it's necessary to make sure the newly elected leader commits at least one Raft transaction on its term (e.g. something similar to what WaitForLeaderWithCommittedOp does). One option is to perform a DDL operation (e.g. add a column) before attempting Raft configuration change corresponding to the replica movement.

I attached the full log of a run where the test scenario failed.