[jira] [Assigned] (KUDU-2943) TsTabletManagerITest.TestTableStats flaky due to WAL/cmeta term disagreement

["Adar Dembo (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KUDU-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adar Dembo reassigned KUDU-2943:
--------------------------------

    Assignee: Adar Dembo

> TsTabletManagerITest.TestTableStats flaky due to WAL/cmeta term disagreement
> ----------------------------------------------------------------------------
>
>                 Key: KUDU-2943
>                 URL: https://issues.apache.org/jira/browse/KUDU-2943
>             Project: Kudu
>          Issue Type: Bug
>          Components: consensus, test
>    Affects Versions: 1.11.0
>            Reporter: Adar Dembo
>            Assignee: Adar Dembo
>            Priority: Critical
>         Attachments: ts_tablet_manager-itest.txt
>
>
> This new test failed in a strange (and worrying) way:
> {noformat}
> /home/jenkins-slave/workspace/kudu-master/1/src/kudu/integration-tests/ts_tablet_manager-itest.cc:753: Failure
> Failed
> Bad status: Corruption: Unable to start RaftConsensus: The last op in the WAL with id 3.4 has a term (3) that is greater than the latest recorded term, which is 2
> {noformat}
> From a brief dig through the code, looks like this means the current term as per the on-disk cmeta file is older than the term in the latest WAL op.
> I can believe that this is somehow due to InternalMiniCluster exercising clean shutdown paths that aren't well tested or robust, but it'd be nice to determine that with certainty.
> I've attached the full test log.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)