[
https://issues.apache.org/jira/browse/AMBARI-14687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15102287#comment-15102287
]
Yusaku Sako commented on AMBARI-14687:
--------------------------------------
The UT failure reported above is Ambari Web but seems unrelated to this patch.
> 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)
