Uploaded image for project: 'Crunch'
  1. Crunch
  2. CRUNCH-458

Eliminate potentially random MR split-point decisions

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.8.4, 0.11.0
    • Component/s: None
    • Labels:
      None

      Description

      I'm running into a pipeline in which the decision of where to split two dependent jobs seems to be random from run-to-run (I only noticed it b/c one of the runs causes the pipeline to throw an NPE, and the other does not.) I'd like to investigate this and try to eliminate any potential sources of randomness in the way that two dependent GBK operations are split.

        Attachments

        1. CRUNCH-458c.patch
          3 kB
          Josh Wills
        2. CRUNCH-458b.patch
          3 kB
          Josh Wills
        3. CRUNCH-458.patch
          2 kB
          Josh Wills

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              jwills Josh Wills
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: