Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 05A4711187 for ; Thu, 24 Apr 2014 03:16:19 +0000 (UTC) Received: (qmail 85850 invoked by uid 500); 24 Apr 2014 03:16:11 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 85746 invoked by uid 500); 24 Apr 2014 03:16:09 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 85737 invoked by uid 99); 24 Apr 2014 03:16:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 03:16:07 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of samliuhadoop@gmail.com designates 209.85.216.49 as permitted sender) Received: from [209.85.216.49] (HELO mail-qa0-f49.google.com) (209.85.216.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Apr 2014 03:16:02 +0000 Received: by mail-qa0-f49.google.com with SMTP id j7so1684434qaq.8 for ; Wed, 23 Apr 2014 20:15:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=YZ2yp2YRTygqc6RC/+Q6Ua6vsjkxT0kJ1FkrQXU+f6Y=; b=dHoCRqjhSQfiD9BQSMwh77obA/fQ+ndwfLU8zuB3wS7ldIDllb55MgJEYWa/GnMJFv ke7C+44WJA69Q5pRjxD4R1VvlDE9N53i2i/SPb/BPMr6BefcLTDBnPwqjEeyJkma318G MzATOKEtFGsvTuh3rxtki3G8Zyxe7on8aSd4bkhXmgwmBzhVsdjIswIXs+/K7C3QZAyQ BJDDQrKxKVu8wksKcx0t1O/ROybItsCnxScsG+NbWT8x0wZqZ3M6s2ivgIZXT7syU2gl MmsEdgK7+wNwtlnd0y34SeoN+zJCgqKxTDdEJtblNfDgmb95DCZhyVOEeCiabIZP+gF3 /CEg== MIME-Version: 1.0 X-Received: by 10.140.96.182 with SMTP id k51mr59442864qge.60.1398309341684; Wed, 23 Apr 2014 20:15:41 -0700 (PDT) Received: by 10.96.56.41 with HTTP; Wed, 23 Apr 2014 20:15:41 -0700 (PDT) In-Reply-To: References: Date: Thu, 24 Apr 2014 11:15:41 +0800 Message-ID: Subject: Re: Differences between HistoryServer and Yarn TimeLine server? From: sam liu To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=001a11391b1698e97f04f7c14329 X-Virus-Checked: Checked by ClamAV on apache.org --001a11391b1698e97f04f7c14329 Content-Type: text/plain; charset=UTF-8 Zhijie, I am much clear now. Thanks a lot! As my understanding, besides previous Job History Server, hadoop now has a new timeline server which could restore both the generic YARN application history and the framework specific information. However, I think the timeline server also include the functions of Job History Server, because it can store the framework specific information(of course, include mapreduce framework). In another words, Job History Server is not necessary any more.* If that's the case, why hadoop still include Job History Server?* 2014-04-23 12:56 GMT+08:00 Zhijie Shen : > In Hadoop 2.4, we have delivered the timeline server at a preview stage, > which actually can serve some generic YARN application history as well as > the framework specific information. Due to the development logistics, we > have created the two concepts: History Server and Timeline Server. To be > simple, you can consider the history server of the service of the generic > YARN application information, while consider the timeline server of the > service of the framework specific information. Importantly, we just have > one daemon, which includes both services, and which we'd like to call > timeline server (unfortunately, the confusing thing is that the command to > start the daemon is "historyserver"). We're going on working on the > timeline server to integrate these two parts, including refactoring the > names. > > BTW, if you mean MapReduce JobHistoryServer by HistoryServer, it's a > different daemon, which serves the historic information of MapReduce jobs > only. > > > On Tue, Apr 22, 2014 at 8:44 PM, sam liu wrote: > >> Hi Experts, >> >> I am confusing on these two concepts. Could you help explain the >> differences? >> >> Thanks! >> > > > > -- > 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. --001a11391b1698e97f04f7c14329 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Zhijie,

I am much clear now. Thanks= a lot!

As my understanding, besides previous Job History Serv= er, hadoop now has a new timeline server which could restore both the gener= ic YARN application history and the framework specific information. However= , I think the timeline server also include the functions of Job History Ser= ver, because it can store the framework specific information(of course, in= clude mapreduce framework). In another words, Job History Server is not nec= essary any more. If that's the case, why hadoop still include Job Hi= story Server?


2014-04-23 12= :56 GMT+08:00 Zhijie Shen <zshen@hortonworks.com>:
In Hadoop 2.4, we have delivered the timeline server = at a preview stage, which actually can serve some generic YARN application = history as well as the framework specific information. Due to the developme= nt logistics, we have created the two concepts: History Server and Timeline= Server. To be simple, you can consider the history server of the service o= f the generic YARN application information, while consider the timeline ser= ver of the service of the framework specific information. Importantly, we j= ust have one daemon, which includes both services, and which we'd like = to call timeline server (unfortunately, the confusing thing is that the com= mand to start the daemon is "historyserver"). We're going on = working on the timeline server to integrate these two parts, including refa= ctoring the names.

BTW, if you mean MapReduce JobHistoryServer by HistoryServer= , it's a different daemon, which serves the historic information of Map= Reduce jobs only.

On Tue, Apr 22, 2014 at 8:44 PM, sam liu <samliuhadoop@gmail.com&= gt; wrote:
Hi Experts,

I am confusing on these= two concepts. Could you help explain the differences?

Thanks= !



--
Zhijie Shen
Hortonworks = Inc.

CONFIDENTIALITY NOTICE
NOTICE: This message is = intended for the use of the individual or entity to which it is addressed a= nd 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, dis= semination, distribution, disclosure or forwarding of this communication is= strictly prohibited. If you have received this communication in error, ple= ase contact the sender immediately and delete it from your system. Thank Yo= u.

--001a11391b1698e97f04f7c14329--