[jira] [Commented] (MESOS-4705) Linux 'perf' parsing logic may fail when OS distribution has perf backports.

["Benjamin Mahler (JIRA)" <ji...@apache.org>]

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

Benjamin Mahler commented on MESOS-4705:
----------------------------------------

[~fan.du] It appears that this doesn't handle my version of perf on CentOS 7.3.1611 with perf version 3.10.0-514.2.2.el7.x86_64.debug:

{noformat}
(statistics).failure(): Failed to parse perf sample: Failed to parse perf sample line '3710583015,,cycles,mesos_test,1459686383,100.00,2.539,GHz': Unexpected number of fields
{noformat}

> Linux 'perf' parsing logic may fail when OS distribution has perf backports.
> ----------------------------------------------------------------------------
>
>                 Key: MESOS-4705
>                 URL: https://issues.apache.org/jira/browse/MESOS-4705
>             Project: Mesos
>          Issue Type: Bug
>          Components: cgroups, isolation
>    Affects Versions: 0.27.1
>            Reporter: Fan Du
>            Assignee: Fan Du
>             Fix For: 0.26.2, 0.27.3, 0.28.2, 1.0.0
>
>
> When sampling container with perf event on Centos7 with kernel 
> 3.10.0-123.el7.x86_64, slave complained with below error spew:
> {code}
> E0218 16:32:00.591181  8376 perf_event.cpp:408] Failed to get perf sample: Failed to parse perf sample: Failed to parse perf sample line '25871993253,,cycles,mesos/5f23ffca-87ed-4ff6-84f2-6ec3d4098ab8,10059827422,100.00': Unexpected number of fields
> {code}
> it's caused by the current perf format [assumption | https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob;f=src/linux/perf.cpp;h=1c113a2b3f57877e132bbd65e01fb2f045132128;hb=HEAD#l430] with kernel version below 3.12 
> On 3.10.0-123.el7.x86_64 kernel, the format is with 6 tokens as below:
> value,unit,event,cgroup,running,ratio
> A local modification fixed this error on my test bed, please review this ticket.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)