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 1029A105AC for ; Wed, 23 Apr 2014 04:57:15 +0000 (UTC) Received: (qmail 2110 invoked by uid 500); 23 Apr 2014 04:57:06 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 1419 invoked by uid 500); 23 Apr 2014 04:57:02 -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 1409 invoked by uid 99); 23 Apr 2014 04:57:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2014 04:57:01 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of zshen@hortonworks.com designates 209.85.192.169 as permitted sender) Received: from [209.85.192.169] (HELO mail-pd0-f169.google.com) (209.85.192.169) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2014 04:56:55 +0000 Received: by mail-pd0-f169.google.com with SMTP id fp1so376161pdb.0 for ; Tue, 22 Apr 2014 21:56:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=QvZ/OU0MCP/2cRQLS3AtBtu52RtAs8HAzmU92vqDD9c=; b=DmdOfMkBQGtEsDIvfWbPYZyNTKN/rlPdus5pr7Vdbb4q7xictHEJ73ue6bgXmmgIxx yLhCzNANxCL9a9jVYiU0VejdbRwNiEaBJHo/ETVzwVZQOM7btZ1CnmCBwq0JtH2z3k72 SyIymWiSrCU7ulw+znB2+pJQDSkSigEwyXgHMBy1NPb0I+kNAhii/xIaJy1tatJ/Ij5t BYgWLm1PT26qUmuBOnTeIRBZ5mUUgn1L2NFujlucmDIYecN4OR5DefxXjUsM2J+S74rc UbfFkpHzbKWWTMOzhsU/O8L/4ty2FeIn3PP9PX5qqoAOuekzEBIarQ8/MPDtVsWOkfNJ J/nA== X-Gm-Message-State: ALoCoQkASzsOSvE/LzZC/Efeu1zoFo3ssMZFQylf8NegSfRpATvT40mHgInjWbom/5g8eafp2g4m7ckVRVq2LWSkgQq2Z3ZDzdnavGVl7G1tCgPiUua18xk= MIME-Version: 1.0 X-Received: by 10.69.25.69 with SMTP id io5mr51469047pbd.22.1398228992473; Tue, 22 Apr 2014 21:56:32 -0700 (PDT) Received: by 10.66.189.131 with HTTP; Tue, 22 Apr 2014 21:56:32 -0700 (PDT) In-Reply-To: References: Date: Tue, 22 Apr 2014 21:56:32 -0700 Message-ID: Subject: Re: Differences between HistoryServer and Yarn TimeLine server? From: Zhijie Shen To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a1134a34a69549c04f7ae8eaf X-Virus-Checked: Checked by ClamAV on apache.org --001a1134a34a69549c04f7ae8eaf Content-Type: text/plain; charset=US-ASCII 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. --001a1134a34a69549c04f7ae8eaf Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
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<= div>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. --001a1134a34a69549c04f7ae8eaf--