[
https://issues.apache.org/jira/browse/AMBARI-17617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371053#comment-15371053
]
Hadoop QA commented on AMBARI-17617:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12817181/AMBARI-17617.patch
against trunk revision .
{color:red}-1 patch{color}. Top-level trunk compilation may be broken.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/7777//console
This message is automatically generated.
> Set default log level for Ranger KMS to INFO
> --------------------------------------------
>
> Key: AMBARI-17617
> URL: https://issues.apache.org/jira/browse/AMBARI-17617
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.4.0
> Reporter: Deepak Sharma
> Assignee: Gautam Borad
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: AMBARI-17617.patch
>
>
> Kms log file is getting bigger till 18 GB , causing No space left on device
> for inode.
> Problem is :
> 1. by default debug log is generated in the kms.log fle
> 2. there is not split in log file if there is over flow of logs in kms.log
> file like other access audit logs file and xa_portal logs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
