incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (HAMA-379) Setting default values to job.setNumBspTask()
Date Tue, 03 May 2011 17:03:03 GMT


Hudson commented on HAMA-379:

-1 overall.  Here are the results of testing the latest attachment
against trunk revision 1098478.

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

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

    patch -1.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> Setting default values to job.setNumBspTask()
> ---------------------------------------------
>                 Key: HAMA-379
>                 URL:
>             Project: Hama
>          Issue Type: Task
>          Components: bsp
>    Affects Versions: 0.2.0
>         Environment: linux
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>            Priority: Minor
>             Fix For: 0.3.0
>         Attachments: hama-379-v2.patch, hama-379.patch
> When a user does not explicitly sets the number of BSP tasks in his own jobs the job
will hang forever with this output:
>     11/04/17 20:07:50 INFO bsp.BSPJobClient: Running job: job_201104172007_0001
>     11/04/17 20:07:53 INFO bsp.BSPJobClient: Current supersteps number: 0
> We should provide a check that will reject wrong values: 1 > numOfTasks > numberOfGrooms
(is this upper bound right or can multiple tasks of the same job run on the same groom?)
> This could be implemented in the method "submitJobInternal" of the BSPJobClient. We should
add an info log statement if we changed the value.

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message