phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ankit Singhal (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2817) Phoenix-Spark plugin doesn't work in secured env
Date Tue, 05 Apr 2016 10:19:25 GMT


Ankit Singhal commented on PHOENIX-2817:

bq. We can, but the match/cases will be still there
do we really need match case and concat after {code} new PhoenixEmbeddedDriver.ConnectionInfo(zkQuorum,
port, znodeParent).toString(){code}

bq. As for kerberos stuff I'm not sure. principal/keytab pair is specific for the particular
machine/session. It's fine when we use it in jdbc driver because we know that all communication
with HBase will be done on this machine, but for MR/Yarn jobs that would not work

I think MR framework serializes the client configuration and made it available in all M/R
context. And bulkload tool(FormatToBytesWritableMapper#setup) in phoenix use it to open connection.
But anyways ,your patch can still work if hbase-site.xml is in class path of client machine
as it will be included in configuration before sending to other nodes.

> Phoenix-Spark plugin doesn't work in secured env
> ------------------------------------------------
>                 Key: PHOENIX-2817
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.4.0, 4.7.0
>            Reporter: Sergey Soldatov
>            Assignee: Sergey Soldatov
>         Attachments: PHOENIX-2817-1.patch, PHOENIX-2817-2.patch, PHOENIX-2817-3.patch
> When phoenix spark plugin is used with secured setup any attempt to perform operation
with PhoenixRDD cause an exception : 
> {noformat}
> Caused by: Login failure for 2181 from keytab /hbase:
Unable to obtain password from user
> 	at
> 	at
> 	at$SecureHadoopUser.login(
> 	at
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl.openConnection(
> 	... 107 more
> Caused by: Unable to obtain password from user
> 	at
> 	at
> 	at
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at
> 	at$000(
> 	at$
> 	at$
> 	at Method)
> 	at
> 	at
> 	at
> 	... 111 more
> {noformat}
> The reason is the how zkUrl is handled in PhoenixRDD: 
> {noformat}
> config.set(HConstants.ZOOKEEPER_QUORUM, url )
> {noformat}
> At the same time the {{ConnectionUtil.getInputConnection}} expects to see all parameters
(quorum address, port, znodeParent) in different Configuration properties. As the result it
gets default values for port and znodeParent and adds it to the provided url, so the {{PhoenixEmbededDriver.create}}
receives something like that:
> {noformat}
> jdbc:phoenix:quorum:2181:/hbase-secure:2181:/hbase
> {noformat}
> and consider 2 fields as kerberos principal and keytab.  

This message was sent by Atlassian JIRA

View raw message