[ 
https://issues.apache.org/jira/browse/KUDU-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16144465#comment-16144465
 ] 

Mike Percy commented on KUDU-2113:
----------------------------------

Nominating this as a 1.5 blocker because it affects our ability to troubleshoot 
broken clusters.

> 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
>
> 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)

Reply via email to