Uploaded image for project: 'Giraph (Retired)'
  1. Giraph (Retired)
  2. GIRAPH-267

Jobs can get killed for not reporting status during INPUT SUPERSTEP

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.0.0
    • 1.0.0
    • graph
    • None

    • Facebook Hadoop

    Description

      Job with a skewed and long (>600secs in my case) INPUT_SUPERSTEP fails for some tasks not reporting their status. From BspServiceWorker#setup(), I could tell while some workers were still loading inputSplits, others finished theirs early and hanged on PredicateLock#waitForever(), and got killed after the timeout.

      Attachments

        1. GIRAPH-267.patch
          13 kB
          Jaeho Shin
        2. GIRAPH-267.patch
          13 kB
          Jaeho Shin
        3. 0001-Made-PredicateLock-report-progress-and-removed-Conte.patch
          11 kB
          Jaeho Shin

        Issue Links

          is related to

          Improvement - An improvement or enhancement to an existing feature or task. GIRAPH-291 PredicateLock should have a constructor to take in a custom waiting time and additional testing

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              netj Jaeho Shin
              netj Jaeho Shin
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: