phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From James Taylor <jamestay...@apache.org>
Subject Re: CDH 5.1
Date Tue, 29 Jul 2014 17:45:11 GMT
FWIW, I got confirmation from another user that Phoenix works fine on CDH 5.1.

Thanks,
James


On Mon, Jul 28, 2014 at 3:57 PM, Jeffrey Zhong <jzhong@hortonworks.com> wrote:
>
> Hey Mike,
>
> It seems you are using wrong Phoenix client to connect Hbase. The
> following stack trace is from HBase0.94. Could you verify that you're
> using right Phoenix 4.0 client? You could use sqlline.py under bin folder
> to test connection.
>
> Thanks,
> -Jeffrey
>
> On 7/28/14, 3:28 PM, "James Taylor" <jamestaylor@apache.org> wrote:
>
>>Thanks for reporting back, Mike. That's disconcerting. The Phoenix
>>jars may need to be rebuilt using the CDH 5.1 jars instead of the open
>>source bits.
>>
>>James
>>
>>On Mon, Jul 28, 2014 at 3:23 PM, Mike Friedman <Mike.Friedman@ds-iq.com>
>>wrote:
>>> On the HBase side, Phoenix seems to be working okay in that no errors
>>>are reported and Cloudera Manager can see all the existing tables. But
>>>the corresponding Phoenix client JAR does not connect. The stack trace
>>>clients receive is reminiscent of what I have seen in the past when
>>>there is an HBase version mismatch. Thank you for any suggestions.
>>>
>>>
>>> An error occurred while establishing the connection:
>>>
>>> Long Message:
>>> Not a host:port pair: PBUF
>>> #
>>> blvdevhdp03.ds-iq.corp
>>>
>>> Details:
>>>    Type: java.lang.IllegalArgumentException
>>>
>>> Stack Trace:
>>> java.lang.IllegalArgumentException: Not a host:port pair: PBUF
>>> blvdevhdp03.ds-iq.corp
>>>    at
>>>org.apache.hadoop.hbase.util.Addressing.parseHostname(Addressing.java:60)
>>>    at org.apache.hadoop.hbase.ServerName.<init>(ServerName.java:101)
>>>    at
>>>org.apache.hadoop.hbase.ServerName.parseVersionedServerName(ServerName.ja
>>>va:283)
>>>    at
>>>org.apache.hadoop.hbase.MasterAddressTracker.bytesToServerName(MasterAddr
>>>essTracker.java:77)
>>>    at
>>>org.apache.hadoop.hbase.MasterAddressTracker.getMasterAddress(MasterAddre
>>>ssTracker.java:61)
>>>    at
>>>org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementati
>>>on.getMaster(HConnectionManager.java:805)
>>>    at
>>>org.apache.hadoop.hbase.client.HBaseAdmin.<init>(HBaseAdmin.java:127)
>>>    at
>>>org.apache.phoenix.query.ConnectionQueryServicesImpl.ensureTableCreated(C
>>>onnectionQueryServicesImpl.java:725)
>>>    at
>>>org.apache.phoenix.query.ConnectionQueryServicesImpl.createTable(Connecti
>>>onQueryServicesImpl.java:1007)
>>>    at
>>>org.apache.phoenix.schema.MetaDataClient.createTableInternal(MetaDataClie
>>>nt.java:1156)
>>>    at
>>>org.apache.phoenix.schema.MetaDataClient.createTable(MetaDataClient.java:
>>>422)
>>>    at
>>>org.apache.phoenix.compile.CreateTableCompiler$2.execute(CreateTableCompi
>>>ler.java:183)
>>>    at
>>>org.apache.phoenix.jdbc.PhoenixStatement.executeMutation(PhoenixStatement
>>>.java:226)
>>>    at
>>>org.apache.phoenix.jdbc.PhoenixStatement.executeUpdate(PhoenixStatement.j
>>>ava:908)
>>>    at
>>>org.apache.phoenix.query.ConnectionQueryServicesImpl.init(ConnectionQuery
>>>ServicesImpl.java:1316)
>>>    at
>>>org.apache.phoenix.jdbc.PhoenixDriver.getConnectionQueryServices(PhoenixD
>>>river.java:122)
>>>    at
>>>org.apache.phoenix.jdbc.PhoenixEmbeddedDriver.connect(PhoenixEmbeddedDriv
>>>er.java:112)
>>>    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>>>    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
>>>    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
>>>    at java.lang.reflect.Method.invoke(Unknown Source)
>>>    at com.onseven.dbvis.g.B.D.?(Z:1413)
>>>    at com.onseven.dbvis.g.B.F$A.call(Z:1474)
>>>    at java.util.concurrent.FutureTask.run(Unknown Source)
>>>    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>>>    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>>>    at java.lang.Thread.run(Unknown Source)
>>>
>>> -----Original Message-----
>>> From: James Taylor [mailto:jamestaylor@apache.org]
>>> Sent: Monday, July 28, 2014 11:35 AM
>>> To: user
>>> Subject: Re: CDH 5.1
>>>
>>> Looks like you may be the first, Mike. If you try it, would you mind
>>>reporting back how it works?
>>>
>>> Thanks,
>>> James
>>>
>>> On Mon, Jul 28, 2014 at 10:52 AM, Alex Kamil <alex.kamil@gmail.com>
>>>wrote:
>>>> Mike, I'm on cdh4, but generally the extra steps are rebuilding
>>>> phoenix with hadoop and hbase jars from cdh, I posted steps here a
>>>> while back, feel free to update:
>>>> https://issues.apache.org/jira/browse/PHOENIX-1041
>>>>
>>>> Alex
>>>>
>>>>
>>>> On Mon, Jul 28, 2014 at 1:32 PM, Mike Friedman
>>>> <Mike.Friedman@ds-iq.com>
>>>> wrote:
>>>>>
>>>>> Has anyone gotten Phoenix to work on CDH5.1? I know theoretically
>>>>> because
>>>>> CDH5.1 includes HBase 0.98, Phoenix should just work but my
>>>>> experience is that that is not the case. It could be just some small
>>>>> additional step to get it going. Any suggestions appreciated.
>>>>>
>>>>>
>>>>> Mike
>>>>>
>>>>> -----Original Message-----
>>>>> From: Mike Friedman [mailto:Mike.Friedman@ds-iq.com]
>>>>> Sent: Saturday, July 19, 2014 7:35 AM
>>>>> To: <user@phoenix.apache.org>
>>>>> Subject: CDH 5.1
>>>>>
>>>>> So now the eagerly awaited CDH 5.1 is out, the distribution that
>>>>> contains HBase 0.98. I am wondering if anyone here has upgraded to
>>>>> it, and has Phoenix core+client working on it. I know Phoenix has
>>>>> been tested with HBase
>>>>> 0.98 per se, but in the full context of CDH 5.1 do people have
>>>>> Phoenix running? Were there any special additional configuration
>>>>> steps you had to do?
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>> Mike
>>>>
>>>>
>
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.

Mime
View raw message