Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8E01F200CFC for ; Thu, 28 Sep 2017 18:01:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8C7611609EC; Thu, 28 Sep 2017 16:01:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D7F261609C2 for ; Thu, 28 Sep 2017 18:01:03 +0200 (CEST) Received: (qmail 21322 invoked by uid 500); 28 Sep 2017 16:01:03 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 21311 invoked by uid 99); 28 Sep 2017 16:01:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Sep 2017 16:01:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 5C8591A0E75 for ; Thu, 28 Sep 2017 16:01:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id MfrS7rKkKu_F for ; Thu, 28 Sep 2017 16:01:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 2B6C260D2C for ; Thu, 28 Sep 2017 16:01:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 79841E041C for ; Thu, 28 Sep 2017 16:01:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 3CE7E242A7 for ; Thu, 28 Sep 2017 16:01:00 +0000 (UTC) Date: Thu, 28 Sep 2017 16:01:00 +0000 (UTC) From: "Tanping Wang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (YARN-7265) Hadoop Server Log Correlation MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 28 Sep 2017 16:01:04 -0000 [ https://issues.apache.org/jira/browse/YARN-7265?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:all-tabpanel ] Tanping Wang updated YARN-7265: ------------------------------- Description: Hadoop has many server logs, yarn tasks logs, node manager= logs, HDFS logs.. There are also a lot of different ways can be used to = expose the logs, build relationship horizontally to correlate the logs or s= earch the logs by keyword. There is a need for a default and yet convenient= logging analytics mechanism in Hadoop itself that at least covers all the= server logs of Hadoop. This log analytics system can correlate the Hadoop= server logs by grouping them by various dimensions including task number, = job number or node number etc. The raw logs with correlation can be easil= y accessed by the application developer or cluster administrator via web pa= ge for managing and debugging. (was: Hadoop has many server logs, yarn tas= ks logs, node manager logs, HDFS logs.. There are also a lot of different= ways can be used to expose the logs, build relationship horizontally to co= rrelate the logs or search the logs by keyword. There is a need for a defau= lt and yet convenient logging analytics mechanism in Hadoop itself that at= least covers all the server logs of Hadoop. This log analytics system can= correlate the Hadoop server logs by grouping them by various dimensions in= cluding task number, job number or node number etc. The raw logs with cor= relation can be easily accessed by the application developer or cluster adm= inistrator.) > Hadoop Server Log Correlation =20 > ------------------------------- > > Key: YARN-7265 > URL: https://issues.apache.org/jira/browse/YARN-7265 > Project: Hadoop YARN > Issue Type: Wish > Components: log-aggregation > Reporter: Tanping Wang > > Hadoop has many server logs, yarn tasks logs, node manager logs, HDFS log= s.. There are also a lot of different ways can be used to expose the logs= , build relationship horizontally to correlate the logs or search the logs = by keyword. There is a need for a default and yet convenient logging analy= tics mechanism in Hadoop itself that at least covers all the server logs of= Hadoop. This log analytics system can correlate the Hadoop server logs by= grouping them by various dimensions including task number, job number or n= ode number etc. The raw logs with correlation can be easily accessed by t= he application developer or cluster administrator via web page for managing= and debugging. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org