Uploaded image for project: 'Samza'
  1. Samza
  2. SAMZA-368

AM UI should show failed container information

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: yarn
    • Labels:
      None

      Description

      All of the most important pieces of information are buried in the AM logs, and not displayed in the UI.

      The AM UI should display all failed containers, along with their exit codes, stack traces, etc. For example:

      Dump of the process-tree for container_1407358862713_0021_01_000002 :
      	|- PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE
      	|- 21565 593 21565 21565 (java) 48828 1620 11089313792 2120985 /export/apps/jdk/JDK-1_8_0_5/bin/java...
      
      Container killed on request. Exit code is 143
      Container exited with a non-zero exit code 143
      

      This stuff will help people debug.

        Attachments

        1. screenshot-samza-368.png
          56 kB
          Aleksandar Bircakovic
        2. SAMZA-368.1.patch
          3 kB
          Aleksandar Bircakovic
        3. SAMZA-368.0.patch
          3 kB
          Aleksandar Bircakovic

          Issue Links

            Activity

              People

              • Assignee:
                a.bircakovic Aleksandar Bircakovic
                Reporter:
                criccomini Chris Riccomini
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: