[
https://issues.apache.org/jira/browse/HAMA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jungblut updated HAMA-379:
---------------------------------
Attachment: (was: hama-379-v4.patch)
> Setting default values to job.setNumBspTask()
> ---------------------------------------------
>
> Key: HAMA-379
> URL: https://issues.apache.org/jira/browse/HAMA-379
> 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-v4.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: http://www.atlassian.com/software/jira
