hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14219) RumenToSLS: parsing problem with crashed attempts
Date Fri, 24 Mar 2017 14:18:41 GMT

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

Hadoop QA commented on HADOOP-14219:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  0s{color} | {color:blue}
Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  8s{color} | {color:red}
HADOOP-14219 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-14219 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12860359/HADOOP-14219.patch
|
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/11916/console |
| Powered by | Apache Yetus 0.5.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> RumenToSLS: parsing problem with crashed attempts
> -------------------------------------------------
>
>                 Key: HADOOP-14219
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14219
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: tools
>    Affects Versions: 2.6.0
>            Reporter: Julien Vaudour
>            Priority: Minor
>         Attachments: HADOOP-14219.patch
>
>
> In case of crashed task attempts, we may have in rumen logs task attempts with null hostName
and finishTime defined to -1
> for example
> {code}
>        {
>           "resourceUsageMetrics": {
>             "heapUsage": 0,
>             "physicalMemoryUsage": 0,
>             "virtualMemoryUsage": 0,
>             "cumulativeCpuUsage": 0
>           },
>           "vmemKbytes": [],
>           "physMemKbytes": [],
>           "cpuUsages": [],
>           "clockSplits": [],
>           "location": null,
>           "sortFinished": -1,
>           "shuffleFinished": -1,
>           "spilledRecords": -1,
>           "reduceOutputRecords": -1,
>           "reduceShuffleBytes": -1,
>           "fileBytesRead": -1,
>           "hdfsBytesWritten": -1,
>           "hdfsBytesRead": -1,
>           "hostName": null,
>           "finishTime": -1,
>           "startTime": 1489619193378,
>           "result": null,
>           "attemptID": "attempt_1488896259152_410442_r_000015_1",
>           "fileBytesWritten": -1,
>           "mapInputRecords": -1,
>           "mapInputBytes": -1,
>           "mapOutputBytes": -1,
>           "mapOutputRecords": -1,
>           "combineInputRecords": -1,
>           "reduceInputGroups": -1,
>           "reduceInputRecords": -1
>         }
> {code}
> Jackson parser will automatically consider -1 as a java.lang.Integer. However RumenToSLSConverter
make the assumption than jackson has deserialize all timstamp as instance of java.lang.Long,
resulting in a ClassCastException.
> RumenToSLSConverter also make the assumption that hostName is not null, so we can also
have a NullPointerException.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message