[
https://issues.apache.org/jira/browse/AMBARI-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406782#comment-15406782
]
Hadoop QA commented on AMBARI-17938:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12821927/AMBARI-17938.v3.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/8276//console
This message is automatically generated.
> Ambari should not recursively chown for HAWQ hdfs upon every start
> ------------------------------------------------------------------
>
> Key: AMBARI-17938
> URL: https://issues.apache.org/jira/browse/AMBARI-17938
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk, 2.4.0
> Reporter: Lav Jain
> Assignee: Lav Jain
> Labels: performance
> Fix For: 2.4.0
>
> Attachments: AMBARI-17938.patch, AMBARI-17938.v2.patch,
> AMBARI-17938.v3.patch
>
>
> This results in changing of owner even if the owner value is same. The
> operation is very costly if there are a lot of subdirectories.
> The owner value only changes when you switch from regular mode to secure mode
> and vice-versa.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
