You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Owen O'Malley (JIRA)" <ji...@apache.org> on 2009/03/17 22:03:50 UTC

[jira] Created: (HADOOP-5519) Remove claims from mapred-default.xml that prime numbers of tasks are helpful.

Remove claims from mapred-default.xml that prime numbers of tasks are helpful.
------------------------------------------------------------------------------

                 Key: HADOOP-5519
                 URL: https://issues.apache.org/jira/browse/HADOOP-5519
             Project: Hadoop Core
          Issue Type: Improvement
          Components: mapred
            Reporter: Owen O'Malley
            Assignee: Owen O'Malley
             Fix For: 0.20.0


There is no value in using prime numbers for numbers of tasks. In fact, most jobs don't even need the number of maps set, since it will increase to the number of blocks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-5519) Remove claims from mapred-default.xml that prime numbers of tasks are helpful.

Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12683331#action_12683331 ] 

Hadoop QA commented on HADOOP-5519:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12402419/remove-prime.patch
  against trunk revision 755790.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified tests.
                        Please justify why no tests are needed for this patch.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 Eclipse classpath. The patch retains Eclipse classpath integrity.

    +1 release audit.  The applied patch does not increase the total number of release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/103/testReport/
Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/103/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/103/artifact/trunk/build/test/checkstyle-errors.html
Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-vesta.apache.org/103/console

This message is automatically generated.

> Remove claims from mapred-default.xml that prime numbers of tasks are helpful.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5519
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5519
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.20.0
>
>         Attachments: remove-prime.patch
>
>
> There is no value in using prime numbers for numbers of tasks. In fact, most jobs don't even need the number of maps set, since it will increase to the number of blocks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (HADOOP-5519) Remove claims from mapred-default.xml that prime numbers of tasks are helpful.

Posted by "Hudson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HADOOP-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12688041#action_12688041 ] 

Hudson commented on HADOOP-5519:
--------------------------------

Integrated in Hadoop-trunk #786 (See [http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/786/])
    . Remove claims from mapred-default.xml that prime numbers of tasks are helpful.  (Owen O'Malley via szetszwo)


> Remove claims from mapred-default.xml that prime numbers of tasks are helpful.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5519
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5519
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.20.0, 0.21.0
>
>         Attachments: remove-prime.patch
>
>
> There is no value in using prime numbers for numbers of tasks. In fact, most jobs don't even need the number of maps set, since it will increase to the number of blocks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-5519) Remove claims from mapred-default.xml that prime numbers of tasks are helpful.

Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen O'Malley updated HADOOP-5519:
----------------------------------

    Status: Patch Available  (was: Open)

> Remove claims from mapred-default.xml that prime numbers of tasks are helpful.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5519
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5519
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.20.0
>
>         Attachments: remove-prime.patch
>
>
> There is no value in using prime numbers for numbers of tasks. In fact, most jobs don't even need the number of maps set, since it will increase to the number of blocks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-5519) Remove claims from mapred-default.xml that prime numbers of tasks are helpful.

Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HADOOP-5519:
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 0.21.0
           Status: Resolved  (was: Patch Available)

I committed this to 0.20 and above.  Thanks, Owen!

> Remove claims from mapred-default.xml that prime numbers of tasks are helpful.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5519
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5519
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.20.0, 0.21.0
>
>         Attachments: remove-prime.patch
>
>
> There is no value in using prime numbers for numbers of tasks. In fact, most jobs don't even need the number of maps set, since it will increase to the number of blocks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-5519) Remove claims from mapred-default.xml that prime numbers of tasks are helpful.

Posted by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tsz Wo (Nicholas), SZE updated HADOOP-5519:
-------------------------------------------

    Hadoop Flags: [Reviewed]

+1 no prime here.

> Remove claims from mapred-default.xml that prime numbers of tasks are helpful.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5519
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5519
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.20.0
>
>         Attachments: remove-prime.patch
>
>
> There is no value in using prime numbers for numbers of tasks. In fact, most jobs don't even need the number of maps set, since it will increase to the number of blocks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HADOOP-5519) Remove claims from mapred-default.xml that prime numbers of tasks are helpful.

Posted by "Owen O'Malley (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HADOOP-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Owen O'Malley updated HADOOP-5519:
----------------------------------

    Attachment: remove-prime.patch

Just removes the confusing advice.

> Remove claims from mapred-default.xml that prime numbers of tasks are helpful.
> ------------------------------------------------------------------------------
>
>                 Key: HADOOP-5519
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5519
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Owen O'Malley
>            Assignee: Owen O'Malley
>             Fix For: 0.20.0
>
>         Attachments: remove-prime.patch
>
>
> There is no value in using prime numbers for numbers of tasks. In fact, most jobs don't even need the number of maps set, since it will increase to the number of blocks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.