[
https://issues.apache.org/jira/browse/AMBARI-19558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15824440#comment-15824440
]
Hadoop QA commented on AMBARI-19558:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12847589/AMBARI-19558.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 6 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/10078//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/10078//console
This message is automatically generated.
> hivemetastore-report.json.tmp permission errors in hive metastore, HS2 logs
> ---------------------------------------------------------------------------
>
> Key: AMBARI-19558
> URL: https://issues.apache.org/jira/browse/AMBARI-19558
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk, 2.5.0
> Reporter: Dmytro Grinenko
> Assignee: Dmytro Grinenko
> Priority: Critical
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19558.patch
>
>
> Noticed that the test cluster has lots of "hivemetastore-report.json.tmp
> (Permission denied)" errors (every 5 seconds).
> It is happening because user hive is running as user custom-hive while only
> user hive has permission for /var/log/hive/ . This location is determined by
> the config hive.service.metrics.file.location, which is set to
> /var/log/hive/hivemetastore-report.json . The log4j logs are going into
> /grid/0/log/hive/.
> A fix would be to change value of this config to use whatever logging
> directory is being used instad of hardcoding to /var/log/hive/. However, we
> are already publishing the metrics via graphana, so this is not needed.
> A quick fix would be to change the config to
> hive.service.metrics.reporter=HADOOP2 in hive-server2-site and hive-metastore
> .
> The old value is -
> hive.service.metrics.reporter=JSON_FILE, JMX, HADOOP2. The suggested change
> above will remove JMX as well, as we anyway aren't setting any of the
> required JMX params. Setting JMX reporter is an unnecessary overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
