You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/03 03:09:00 UTC

[jira] [Updated] (KUDU-2522) Add a stress test for ksck

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

Grant Henke updated KUDU-2522:
------------------------------
    Component/s: test

> Add a stress test for ksck
> --------------------------
>
>                 Key: KUDU-2522
>                 URL: https://issues.apache.org/jira/browse/KUDU-2522
>             Project: Kudu
>          Issue Type: Improvement
>          Components: ops-tooling, supportability, test
>    Affects Versions: 1.8.0
>            Reporter: William Berkeley
>            Assignee: William Berkeley
>            Priority: Major
>
> We had a problem in the past where ksck could segfault when run against a cluster at the wrong time (KUDU-2113). It's really a bummer to have tools fail when you need them to help investigate or fix a problem. We should add some kind of integration test that runs ksck against clusters with restarting nodes to make sure ksck isn't prone to crashing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)