ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hitesh Shah (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-17186) Tez View: Improve proxy logging
Date Thu, 23 Jun 2016 20:19:16 GMT

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

Hitesh Shah commented on AMBARI-17186:
--------------------------------------

Updated with review comments 

> Tez View: Improve proxy logging
> -------------------------------
>
>                 Key: AMBARI-17186
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17186
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Sreenath Somarajapuram
>            Priority: Blocker
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17186.1.patch, AMBARI-17186.2.patch, AMBARI-17186.3.patch,
AMBARI-17186.4.patch
>
>
> More log messages would help us to debug EARs faster.
> # Add error log when configuration fetch fails.
> # Add debug log when request proxying / redirection succeed
> # Add error log when request proxying / redirection fails
> With effect from AMBARI-14084, each view would have separate log file.
> - For Tez view that is /var/log/ambari-server/tez-view/tez-view.log.
> - Debug log would be logged only when the debug mode is enabled. (Set log4j.logger.org.apache.ambari.view.tez=DEBUG,tezView
in view.log4j.properties for the same)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message