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

Hadoop QA commented on AMBARI-14687:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12782520/AMBARI-14687.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-web.

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/4937//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/4937//console

This message is automatically generated.

> adding additional hive hosts via ambari did not update the proxy settings in 
> hadoop   
> ------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14687
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14687
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-14687.patch
>
>
> On my cluster i added 1 additional host to run the metastore and one 
> additional host to run the HS2. 
> However in the proxy settings for hive in hadoop configs we only have the 
> original single host.
> Configs like: hadoop.proxyuser.hive.hosts, hadoop.proxyuser.hcat.hosts
> Because of this we see failures lile
> {code}
> org.apache.hive.service.cli.HiveSQLException: Failed to open new session: 
> java.lang.RuntimeException: java.lang.RuntimeException: 
> org.apache.hadoop.ipc.RemoteException(org.apache.hadoop.security.authorize.AuthorizationException):
>  Unauthorized connection for super-user: 
> hive/[email protected] from IP 172.22.64.65
>         at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:258)
>         at org.apache.hive.jdbc.Utils.verifySuccess(Utils.java:249)
>         at 
> org.apache.hive.jdbc.HiveConnection.openSession(HiveConnection.java:565)
>         at org.apache.hive.jdbc.HiveConnection.<init>(HiveConnection.java:171)
>         at org.apache.hive.jdbc.HiveDriver.connect(HiveDriver.java:105)
>         at java.sql.DriverManager.getConnection(DriverManager.java:664)
>         at java.sql.DriverManager.getConnection(DriverManager.java:270)
>         at 
> org.apache.oozie.action.hadoop.Hive2Credentials.addtoJobConf(Hive2Credentials.java:64)
>         at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1213)
>         at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1073)
>         at 
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1293)
>         at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:250)
>         at 
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:64)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:286)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:356)
>         at 
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:434)
>         at 
> org.apache.oozie.command.wf.SignalXCommand.execute(SignalXCommand.java:76)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:286)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:356)
>         at 
> org.apache.oozie.command.wf.ActionEndXCommand.execute(ActionEndXCommand.java:280)
>         at 
> org.apache.oozie.command.wf.ActionEndXCommand.execute(ActionEndXCommand.java:61)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:286)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:356)
>         at 
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:244)
>         at 
> org.apache.oozie.command.wf.ActionCheckXCommand.execute(ActionCheckXCommand.java:56)
>         at org.apache.oozie.command.XCommand.call(XCommand.java:286)
>         at 
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:175)
>         at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>         at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>         at java.lang.Thread.run(Thread.java:745)
> {code}



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

Reply via email to