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 148E8200BBA for ; Sat, 22 Oct 2016 02:13:01 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 132D0160AE8; Sat, 22 Oct 2016 00:13:01 +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 F2CC3160AE9 for ; Sat, 22 Oct 2016 02:12:59 +0200 (CEST) Received: (qmail 35254 invoked by uid 500); 22 Oct 2016 00:12:58 -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 35218 invoked by uid 99); 22 Oct 2016 00:12:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Oct 2016 00:12:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A46642C2A67 for ; Sat, 22 Oct 2016 00:12:58 +0000 (UTC) Date: Sat, 22 Oct 2016 00:12:58 +0000 (UTC) From: "Botong Huang (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (YARN-5525) Make log aggregation service class configurable MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Sat, 22 Oct 2016 00:13:01 -0000 [ https://issues.apache.org/jira/browse/YARN-5525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15596356#comment-15596356 ] Botong Huang edited comment on YARN-5525 at 10/22/16 12:12 AM: --------------------------------------------------------------- What if the cluster provider doesn't want to use the existing {{AppLogAggregator}} at all, then they need to ask all their user to set the customized aggregator in {{LogAggregationContext}} for all jobs. Why don't we make the default/fallback implementation also configurable? was (Author: botong): What if the cluster provider doesn't want to use the existing {{AppLogAggregator}} at all, then they need to ask for user to set the customized aggregator in {{LogAggregationContext}} for all jobs. Why don't we make the default/fallback implementation also configurable? > Make log aggregation service class configurable > ----------------------------------------------- > > Key: YARN-5525 > URL: https://issues.apache.org/jira/browse/YARN-5525 > Project: Hadoop YARN > Issue Type: Improvement > Components: log-aggregation > Reporter: Giovanni Matteo Fumarola > Assignee: Botong Huang > Priority: Minor > Attachments: YARN-5525.v1.patch, YARN-5525.v2.patch, YARN-5525.v3.patch > > > Make the log aggregation class configurable and extensible, so that alternative log aggregation behaviors like app specific log aggregation directory, log aggregation format can be implemented and plugged in. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: yarn-issues-help@hadoop.apache.org