You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Thomas Jungblut (JIRA)" <ji...@apache.org> on 2012/10/17 22:46:05 UTC
[jira] [Commented] (HAMA-613) Scheduler kills job too silently when
out of slots
[ https://issues.apache.org/jira/browse/HAMA-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478356#comment-13478356 ]
Thomas Jungblut commented on HAMA-613:
--------------------------------------
Sorry lost track of this. I have put this on my TODO list and will review tomorrow.
Thanks!
> Scheduler kills job too silently when out of slots
> --------------------------------------------------
>
> Key: HAMA-613
> URL: https://issues.apache.org/jira/browse/HAMA-613
> Project: Hama
> Issue Type: Bug
> Components: bsp core
> Affects Versions: 0.5.0
> Reporter: Thomas Jungblut
> Assignee: Yuesheng Hu
> Priority: Blocker
> Fix For: 0.6.0
>
> Attachments: HAMA-613.patch
>
>
> If for example a user submits two text files as input, it will sometimes be split in 4 chunks.
> This usually exceeds the number of tasks that are available in the cluster (if out of the box installation just have 3 tasks configured).
> Mainly two questions that pop into my mind:
> -Why are two text files split into 4 tasks if the BSPJobClient should check if it exceeds the number of available task slots?
> -Why does the Client schedules the job if it knows that there are not enough slots available?
> Of course this should yield into a less cryptic error message. Well, actually currently there is no error messages, constantly confusing users.
> This is a blocker for 0.6.
--
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