Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 1 Apr 2014 23:07:17 +0000 (UTC)
From: "Jian He (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12704216.1396002910333.47755.1396393637726@arcas>
In-Reply-To: <JIRA.12704216.1396002910333@arcas>
References: <JIRA.12704216.1396002910333@arcas>
Subject: [jira] [Commented] (YARN-1890) Too many unnecessary logs are logged
 while accessing applicationMaster web UI.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/YARN-1890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13957128#comment-13957128 ] 

Jian He commented on YARN-1890:
-------------------------------

Agree with moving the verbose access logging into debug level. Maybe also have some place just print a single logging about the accessing user in INFO level, which is good for debugging.? 

> Too many unnecessary logs are logged while accessing applicationMaster web UI.
> ------------------------------------------------------------------------------
>
>                 Key: YARN-1890
>                 URL: https://issues.apache.org/jira/browse/YARN-1890
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Rohith
>            Assignee: Rohith
>            Priority: Minor
>         Attachments: YARN-1890.patch
>
>
> Accessing applicationMaster UI which is redirected from RM UI, logs too many logs in ResourceManager logs and ProxyServer logs. On every refresh, logging is done at WebAppProxyServlet.doGet(). All my RM and Proxyserver logs are filled with UI information logs which are not really necessary for user.


--
This message was sent by Atlassian JIRA
(v6.2#6252)