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

Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2017/07/28 16:45:01 UTC

[jira] [Resolved] (KUDU-1536) KSCK can crash when run against newly started master with existing tables

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

Todd Lipcon resolved KUDU-1536.
-------------------------------
       Resolution: Fixed
         Assignee: David Alves  (was: Will Berkeley)
    Fix Version/s: 1.5.0

David fixed this in commit def06d8b8155d2aa5838d19f00cce940d2233ad1

> KSCK can crash when run against newly started master with existing tables
> -------------------------------------------------------------------------
>
>                 Key: KUDU-1536
>                 URL: https://issues.apache.org/jira/browse/KUDU-1536
>             Project: Kudu
>          Issue Type: Bug
>          Components: ksck
>            Reporter: Dan Burkert
>            Assignee: David Alves
>             Fix For: 1.5.0
>
>         Attachments: alter_table-randomized-test.txt
>
>
> [This line|https://github.com/apache/incubator-kudu/blob/master/src/kudu/tools/ksck.cc#L329] assumes that the master returns all tablet servers, but this isn't necessarily the case when the master is newly started and hasn't yet processed all heartbeats.  Full test log attached.



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