Dinesh Bhat updated KUDU-1699:
    Attachment: delete_table-test.txt

> Make the tests less failure-prone for 'Timed out waiting for Table Creation'
> ----------------------------------------------------------------------------
>                 Key: KUDU-1699
>                 URL: https://issues.apache.org/jira/browse/KUDU-1699
>             Project: Kudu
>          Issue Type: Bug
>          Components: test
>            Reporter: Dinesh Bhat
>            Assignee: Dinesh Bhat
>         Attachments: 
> 643ab5a4a0500d3bd819ebb7d07e431da2bea7ff_161.0.delete_table_test_2.zip, 
> a2d6375b7fe1fa1e483dce49157a53dde714d372_40.0.create_table_itest_0.zip, 
> create-table-itest.txt, delete_table-test.txt
> Triaging one issue (which I believe is not related to network flake) I found 
> while testing the 1.0.1 RC release bits for tracking purposes. I noticed that 
> the failure pattern for some of these tests are quite common. Here are the 
> sequences of operations from logs just before failure:
>  - ExternalMiniClusterITestBase::StartCluster() succeeds creating the tablet 
> servers to hold tablet replicas
>  - TestTable is created either directly from test or via 
> TestWorkload.Setup(), so tablet replicas are spilled to the tablet servers.
>  - Meanwhile the tablet replicas haven't elected a leader successfully (only 
> terms are advanced for about 30 secs), and eventually table create fails.
> It is not clear to me if this is a bug, I need to dig into this little more 
> than just logs. If this is not a bug, I wonder if we have some room to make 
> this less failure-prone here. Attached are 2 logs I have from the test run.

This message was sent by Atlassian JIRA

Reply via email to