hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Zhijie Shen <zs...@hortonworks.com>
Subject [Discussion] Merge YARN-321 into Branch-2
Date Mon, 06 Jan 2014 02:22:11 GMT
Hi folks,

Majority of the functionality of Application History Server has been
completed on branch YARN-321. AHS can now work end-to-end. ResourceManager
records the historical information of the application, the application
attempt and the container in terms of events via a history writer on a
separate thread. The historical information is going to be persisted on
HDFS. On the other side, an application history server runs as a separate
process, and it allows users to access the historical information via RPC
interface, web UI and REST APIs.

According to the proposal, the only major missing piece is security. Except
it, YARN-321 should be pretty much ready to be merged to Branch-2. We
propose to merge YARN-321 to Branch-2 now, such that we can prevent
YARN-321 from falling behind too much, and reduce the effort of editing
merge conflicts. After merge, we can continue on security, refactoring
duplicate code, fixing bugs and other improvements.

Anyone who is interested in looking at AHS can review/play with YARN-321
branch: http://svn.apache.org/viewvc/hadoop/common/branches/YARN-321/

You can also have a look at the latest design doc:
https://issues.apache.org/jira/secure/attachment/12619638/Generic%20Application%20History%20-%20Design-20131219.pdf

If there are no objections, we'll push towards updating the branch, running
the patch through Jenkins and getting ready for merge vote by the end of
this week.

Thanks,
Zhijie

-- 
Zhijie Shen
Hortonworks Inc.
http://hortonworks.com/

-- 
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message