Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.8.0
    • Fix Version/s: None
    • Component/s: webapp
    • Labels:
      None

      Description

      The application attempts page (http://RM:8088/cluster/appattempt/appattempt_1431101480046_0003_000001)

      is a bit confusing on what is going on. I think the table of containers there is for only Running containers and when the app is completed or killed its empty. The table should have a label on it stating so.

      Also the "AM Container" field is a link when running but not when its killed. That might be confusing.

      There is no link to the logs in this page but there is in the app attempt table when looking at http://
      rm:8088/cluster/app/application_1431101480046_0003

      1. 0001-YARN-3603.patch
        8 kB
        Sunil G
      2. 0002-YARN-3603.patch
        9 kB
        Sunil G
      3. 0003-YARN-3603.patch
        9 kB
        Sunil G
      4. ahs1.png
        275 kB
        Sunil G

        Activity

        Hide
        sunilg Sunil G added a comment -

        I think this patch has gone stale and I feel we can move this ticket forward.
        Rohith Sharma K S / Xuan Gong / Thomas Graves Could you please help to check the screen shots attached and see if its a good addition.

        Also would like to propose one point which got discussed with Jeff about killed container. Is it good to have that information in RM UI. Any known reasons why we do not have killed/preempted container list in UI.
        Thank You.

        Show
        sunilg Sunil G added a comment - I think this patch has gone stale and I feel we can move this ticket forward. Rohith Sharma K S / Xuan Gong / Thomas Graves Could you please help to check the screen shots attached and see if its a good addition. Also would like to propose one point which got discussed with Jeff about killed container. Is it good to have that information in RM UI. Any known reasons why we do not have killed/preempted container list in UI. Thank You.
        Hide
        sunilg Sunil G added a comment -

        Hi Jeff Zhang
        Thank you for sharing the thoughts. I could remember an old JIRA YARN-1809, where UI is made similar for RM and HistoryServer.
        Here we use {{getContainers)), where History/Timeline fills containers info from ApplicationContext (has all container info). But RM was taking from RMContext where only live containers are taken. I understood the need of killed containers here. it can help in debugging. However we have to segregate killed/preempted containers from completed containers.

        Hi Wangda Tan
        I also feel that we can have the information about killed/preempted container along with running containers in app attempt UI. In YARN-1809, we added for only running containers. Could you pls share your thoughts here.

        Show
        sunilg Sunil G added a comment - Hi Jeff Zhang Thank you for sharing the thoughts. I could remember an old JIRA YARN-1809 , where UI is made similar for RM and HistoryServer. Here we use {{getContainers)), where History/Timeline fills containers info from ApplicationContext (has all container info). But RM was taking from RMContext where only live containers are taken. I understood the need of killed containers here. it can help in debugging. However we have to segregate killed/preempted containers from completed containers. Hi Wangda Tan I also feel that we can have the information about killed/preempted container along with running containers in app attempt UI. In YARN-1809 , we added for only running containers. Could you pls share your thoughts here.
        Hide
        zjffdu Jeff Zhang added a comment -

        Still feel excluding failed container doesn't make sense. If some of my containers fail during job running, how can I check its logs through web ui if I don't want to kill the job ?

        Show
        zjffdu Jeff Zhang added a comment - Still feel excluding failed container doesn't make sense. If some of my containers fail during job running, how can I check its logs through web ui if I don't want to kill the job ?
        Hide
        sunilg Sunil G added a comment -

        Hi Jeff Zhang
        Thank you for pointing this. Container Exit Status must not be present in AppAttempt page. I will remove the same and upload a patch.

        For RM WebUI, we are using ClientRMService alone, and ATS/AHS is not contacted here to get container info. Also RM keeps tracks of running containers here and the idea is to keep information about completed containers in ATS/AHS UI. When application is finished/running, ATS UI is capable of giving detailed information about the application (containers info also).

        Show
        sunilg Sunil G added a comment - Hi Jeff Zhang Thank you for pointing this. Container Exit Status must not be present in AppAttempt page. I will remove the same and upload a patch. For RM WebUI, we are using ClientRMService alone, and ATS/AHS is not contacted here to get container info. Also RM keeps tracks of running containers here and the idea is to keep information about completed containers in ATS/AHS UI. When application is finished/running, ATS UI is capable of giving detailed information about the application (containers info also).
        Hide
        zjffdu Jeff Zhang added a comment -

        Sunil G If it is "Running Container ID", is it still necessary to include "Container Exit Status" ? And any reasons to exclude the killed containers here ? I think it would be helpful to diagnose if all the containers are included.

        Show
        zjffdu Jeff Zhang added a comment - Sunil G If it is "Running Container ID", is it still necessary to include "Container Exit Status" ? And any reasons to exclude the killed containers here ? I think it would be helpful to diagnose if all the containers are included.
        Hide
        sunilg Sunil G added a comment -

        Rebasing patch against latest trunk.

        Show
        sunilg Sunil G added a comment - Rebasing patch against latest trunk.
        Hide
        sunilg Sunil G added a comment -

        Thomas Graves Could you please take a look on the screen shot which I attached and share your opinion.

        Show
        sunilg Sunil G added a comment - Thomas Graves Could you please take a look on the screen shot which I attached and share your opinion.
        Hide
        sunilg Sunil G added a comment -

        Attaching an updated version of patch. Also attaching screen shots of UI. Thomas Graves Could u please take a look on this. Thank you.

        Show
        sunilg Sunil G added a comment - Attaching an updated version of patch. Also attaching screen shots of UI. Thomas Graves Could u please take a look on this. Thank you.
        Hide
        sunilg Sunil G added a comment -

        Uploading an initial version patch.

        • "Container ID" is shown only for Running containers in App Attempt page. Change the column name to "Running Container ID"
        • "AM Container" is showing the container link when Attempt is running, else showing the container ID in plain text. Here we can change label to "AM Container Link" in case when AM is running and "AM Container ID" while AM is finished or killed
        • AM Container logs are shown in App page but not app attempt page. An entry is added for same as "AM Container Logs"
        Show
        sunilg Sunil G added a comment - Uploading an initial version patch. "Container ID" is shown only for Running containers in App Attempt page. Change the column name to "Running Container ID" "AM Container" is showing the container link when Attempt is running, else showing the container ID in plain text. Here we can change label to "AM Container Link" in case when AM is running and "AM Container ID" while AM is finished or killed AM Container logs are shown in App page but not app attempt page. An entry is added for same as "AM Container Logs"
        Hide
        tgraves Thomas Graves added a comment -

        go for it. Thanks!

        Show
        tgraves Thomas Graves added a comment - go for it. Thanks!
        Hide
        sunilg Sunil G added a comment -

        I would like to work on this. Would u mind if I take this.

        Thank u...

        Show
        sunilg Sunil G added a comment - I would like to work on this. Would u mind if I take this. Thank u...

          People

          • Assignee:
            sunilg Sunil G
            Reporter:
            tgraves Thomas Graves
          • Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

            • Created:
              Updated:

              Development