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

Posted to issues@kudu.apache.org by "Adar Dembo (JIRA)" <ji...@apache.org> on 2019/03/07 04:47:00 UTC

[jira] [Resolved] (KUDU-2721) CHECK can be hit when there are gaps in present CPU numbers

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

Adar Dembo resolved KUDU-2721.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

Tim fixed this in commit feebbb264. Thanks, Tim!

> CHECK can be hit when there are gaps in present CPU numbers
> -----------------------------------------------------------
>
>                 Key: KUDU-2721
>                 URL: https://issues.apache.org/jira/browse/KUDU-2721
>             Project: Kudu
>          Issue Type: Bug
>    Affects Versions: 1.8.0
>         Environment: SLES12-SP3
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Critical
>              Labels: crash
>             Fix For: 1.10.0
>
>         Attachments: cpus.cc
>
>
> We saw a case where Impala is crashing in the Kudu client and it seems to be because the "present" string can have multiple ranges in it - "0-15,32-47\n" in this case.  See https://github.com/apache/kudu/blob/148a0c7bec6554724339a2235cbd723fb74be339/src/kudu/gutil/sysinfo.cc#L177
> I've attached a small test program based on the code illustrating that the assert gets hit.
> I think we should figure out all of the possible formats for the present string and make sure we handle them. Or figure out a different way to get equivalent info.
> A workaround for the case that we saw was to disable hyperthreading, which changed the string to being a single range.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)