hadoop-mapreduce-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] (MAPREDUCE-6467) Submitting streaming job is not thread safe
Date Thu, 28 Sep 2017 22:27:01 GMT

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

Hadoop QA commented on MAPREDUCE-6467:
--------------------------------------

| (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  5s{color} | {color:red}
MAPREDUCE-6467 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | MAPREDUCE-6467 |
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12764304/MAPREDUCE-6467.001.patch
|
| Console output | https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/7162/console |
| Powered by | Apache Yetus 0.5.0   http://yetus.apache.org |


This message was automatically generated.



> Submitting streaming job is not thread safe
> -------------------------------------------
>
>                 Key: MAPREDUCE-6467
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6467
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: job submission
>    Affects Versions: 2.7.1
>            Reporter: jeremie simon
>            Assignee: Ivo Udelsmann
>            Priority: Minor
>              Labels: easyfix, streaming, thread-safety
>         Attachments: MAPREDUCE-6467.001.patch
>
>
> The submission of the streaming job is not thread safe. 
> That is because the class StreamJob is using the OptionBuilder which is itself not thread
safe. 
> This can cause super tricky bugs. 
> An easy fix would be to simply create instances of Option through the normal constructor
and decorate the object if necessary. 
> This fix should be applied on the functions createOption and createBoolOption. 



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

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


Mime
View raw message