You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2019/10/16 18:12:00 UTC
[jira] [Created] (KUDU-2976) MoveTabletParamTest.Test is flaky
Alexey Serbin created KUDU-2976:
-----------------------------------
Summary: MoveTabletParamTest.Test is flaky
Key: KUDU-2976
URL: https://issues.apache.org/jira/browse/KUDU-2976
Project: Kudu
Issue Type: Bug
Components: test
Reporter: Alexey Serbin
Attachments: kudu-admin-test.7.txt.xz
The test in {{EnableKudu1097AndDownTS/MoveTabletParamTest.Test/0}} configuration sometime fails with the following error message:
{noformat}
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
{noformat}
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)