Description
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.