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 02:50:00 UTC

[jira] [Resolved] (KUDU-2424) Track cluster startup with ksck

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

Grant Henke resolved KUDU-2424.
-------------------------------
    Fix Version/s: NA
       Resolution: Duplicate

> Track cluster startup with ksck
> -------------------------------
>
>                 Key: KUDU-2424
>                 URL: https://issues.apache.org/jira/browse/KUDU-2424
>             Project: Kudu
>          Issue Type: Improvement
>          Components: ksck, ops-tooling
>    Affects Versions: 1.7.0
>            Reporter: William Berkeley
>            Assignee: William Berkeley
>            Priority: Major
>             Fix For: NA
>
>
> Right now, ksck is probably the best way to track a cluster's progress towards being fully started and ready to go. However, it doesn't track bootstrap explicitly. It might be nice if it could. This would need server-side changes to expos information about bootstrapping, I think.



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