Uploaded image for project: 'Crunch (Retired)'
  1. Crunch (Retired)
  2. CRUNCH-355

Rename jobs to show how many stages have done before job submission

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.10.0, 0.8.3
    • Core
    • None

    Description

      The naming mechanism introduced in CRUNCH-262 has a flaw. It adds (m/n) to the end of job name, where m is the current stage number at planning time and n is the total number of stages.

      Suppose in the following case, where A takes a long time to run, when B is submitted, C and D have completed. As there are 3 jobs done, we should expect B to be (4/5) rather than (2/5) or (3/5).

      
      

      A C

       

      B D
      \ /
      E

      {/code}

      In planning time, we don't have a clue which stage will complete earlier. So I think it better to assign it at runtime.

      One problem here is that the user may access to Job instance before it submits. So he may observe a sudden change of job name.

      Attachments

        1. CRUNCH-355.patch
          10 kB
          Josh Wills

        Activity

          People

            jwills Josh Wills
            stepinto Chao Shi
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: