[
https://issues.apache.org/jira/browse/AMBARI-16031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253507#comment-15253507
]
Hadoop QA commented on AMBARI-16031:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12800144/AMBARI-16031.trunk.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 1 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 ambari-web.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/6599//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/6599//console
This message is automatically generated.
> Create "/hadoop/llap/local" on each host and disk in Kerberized cluster for
> LLAP
> --------------------------------------------------------------------------------
>
> Key: AMBARI-16031
> URL: https://issues.apache.org/jira/browse/AMBARI-16031
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
> Affects Versions: 2.4.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.4.0
>
> Attachments: AMBARI-16031.trunk.patch
>
>
> - In non-kerberized cluster, hive.llap.daemon.work.dir will point to :
> "$\{yarn.nodemanager.local-dirs\}”
> - In kerberized cluster, we need to create "/hadoop/llap/local" on each node
> and disk and have "hive.llap.daemon.work.dirs" point to it.
> - It's similar to the way yarn.nodemanager.local-dirs is created.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
