Uploaded image for project: 'Hama'
  1. Hama
  2. HAMA-379

Setting default values to job.setNumBspTask()

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 0.2.0
    • 0.3.0
    • bsp core
    • None
    • linux

    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.

      Attachments

        1. HAMA-379_v07.patch
          4 kB
          Edward J. Yoon
        2. hama-379-v4.patch
          1 kB
          Thomas Jungblut
        3. hama-379-v5.patch
          2 kB
          Edward J. Yoon
        4. hama-379-v6.patch
          2 kB
          Edward J. Yoon

        Activity

          People

            thomas.jungblut Thomas Jungblut
            thomas.jungblut Thomas Jungblut
            Votes:
            2 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: