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

Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2017/08/29 16:24:00 UTC

[jira] [Resolved] (KUDU-2113) SEGV running ksck while cluster was starting up

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

Will Berkeley resolved KUDU-2113.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.6.0

Fixed in b54eab1f31dd2180e103f1cddbaa2194396396c5

> SEGV running ksck while cluster was starting up
> -----------------------------------------------
>
>                 Key: KUDU-2113
>                 URL: https://issues.apache.org/jira/browse/KUDU-2113
>             Project: Kudu
>          Issue Type: Bug
>          Components: ksck
>    Affects Versions: 1.5.0
>            Reporter: Todd Lipcon
>            Assignee: Will Berkeley
>            Priority: Blocker
>             Fix For: 1.6.0
>
>
> I just ran ksck against a cluster while it was in the process of starting up and got a SEGV. By the time I hooked up gdb to a debug build it was no longer SEGVing so I don't have a lot of info, but I did catch one stack trace and saw the crash is in VerifyTablet.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)