Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03D93103EC for ; Mon, 17 Mar 2014 18:51:47 +0000 (UTC) Received: (qmail 78016 invoked by uid 500); 17 Mar 2014 18:51:46 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 77820 invoked by uid 500); 17 Mar 2014 18:51:44 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 77809 invoked by uid 99); 17 Mar 2014 18:51:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Mar 2014 18:51:43 +0000 Date: Mon, 17 Mar 2014 18:51:43 +0000 (UTC) From: "Vinod Kumar Vavilapalli (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-1844) yarn.log.server.url should have a default value MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938197#comment-13938197 ] Vinod Kumar Vavilapalli commented on YARN-1844: ----------------------------------------------- Yes, makes sense. Once ATS (YARN-1530) is production ready, we should point this URL to that by default. > yarn.log.server.url should have a default value > ----------------------------------------------- > > Key: YARN-1844 > URL: https://issues.apache.org/jira/browse/YARN-1844 > Project: Hadoop YARN > Issue Type: Improvement > Components: nodemanager > Affects Versions: 2.3.0 > Reporter: Jason Lowe > > Currently yarn.log.server.url must be configured properly by a user when log aggregation is enabled so logs to continue to be served from their original URL after they've been aggregated. It would be nice if a default value for this property could be provided that would work "out of the box" for at least simple cluster setups (i.e.: already point to JHS or AHS accordingly). -- This message was sent by Atlassian JIRA (v6.2#6252)