Alexey Serbin created KUDU-2337:
-----------------------------------

             Summary: Enable at least one reader thread in TestWorkload in 
RaftConsensusStressITest::RemoveReplaceInCycle
                 Key: KUDU-2337
                 URL: https://issues.apache.org/jira/browse/KUDU-2337
             Project: Kudu
          Issue Type: Test
          Components: test
            Reporter: Alexey Serbin


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:

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



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to