Uploaded image for project: 'Hadoop YARN'
  1. Hadoop YARN
  2. YARN-321

[Umbrella] Generic application history service

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      The mapreduce job history server currently needs to be deployed as a trusted server in sync with the mapreduce runtime. Every new application would need a similar application history server. Having to deploy O(T*V) (where T is number of type of application, V is number of version of application) trusted servers is clearly not scalable.

      Job history storage handling itself is pretty generic: move the logs and history data into a particular directory for later serving. Job history data is already stored as json (or binary avro). I propose that we create only one trusted application history server, which can have a generic UI (display json as a tree of strings) as well. Specific application/version can deploy untrusted webapps (a la AMs) to query the application history server and interpret the json for its specific UI and/or analytics.

        Attachments

        1. Generic Application History - Design-20131219.pdf
          103 kB
          Vinod Kumar Vavilapalli
        2. ApplicationHistoryServiceHighLevel.pdf
          55 kB
          Sandy Ryza
        3. AHS Diagram.pdf
          287 kB
          Zhijie Shen
        4. HistoryStorageDemo.java
          3 kB
          Zhijie Shen

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                vicaya Luke Lu
              • Votes:
                1 Vote for this issue
                Watchers:
                72 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: