hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4949) Enable multiple pi jobs to run in parallel
Date Sat, 02 Feb 2013 12:42:23 GMT

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

Hudson commented on MAPREDUCE-4949:
-----------------------------------

Integrated in Hadoop-Hdfs-0.23-Build #513 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/513/])
    MAPREDUCE-4949. Enable multiple pi jobs to run in parallel. (sandyr via tucu) (Revision
1441589)

     Result = SUCCESS
tgraves : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1441589
Files : 
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt
* /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-mapreduce-examples/src/main/java/org/apache/hadoop/examples/QuasiMonteCarlo.java

                
> Enable multiple pi jobs to run in parallel
> ------------------------------------------
>
>                 Key: MAPREDUCE-4949
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4949
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: examples
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>            Priority: Minor
>             Fix For: 2.0.3-alpha, 0.23.7
>
>         Attachments: MAPREDUCE-4949.patch
>
>
> Currently the hadoop pi example uses a hardcoded temporary directory to store its inputs
and outputs.  This makes it so that only one pi job can run at a time, and that if it is cancelled,
the temporary directory must be manually deleted.
> I propose using a temporary directory based on a timestamp and random number to avoid
these conflicts

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message