[KUDU-2337] Enable at least one reader thread in TestWorkload in RaftConsensusStressITest::RemoveReplaceInCycle

• Type: Test
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: test
• Assignee: Unassigned
• Reporter: Alexey Serbin
• Created: 13/Mar/18 00:00
• Updated: 13/Mar/18 00:00

Description

Once leader leases are implemented or some retry technique is implemented to overcome the mismatch of between the number of written and read rows in TestWorkload, enable at least one reader thread for TestWorkload in RaftConsensusStressITest::RemoveReplaceInCycle.

As for now, if enabling at least one read thread, the RaftConsensusStressITest::RemoveReplaceInCycle scenario time to time hits the assert at https://github.com/apache/kudu/blob/master/src/kudu/integration-tests/test_workload.cc#L236 with messages like below:

Check failed: row_count >= expected_row_count (31049 vs. 31050)