phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stan Campbell <stan.campbe...@gmail.com>
Subject Re: Phoenix and CDH 5 (HBase 0.96)
Date Fri, 13 Jun 2014 16:40:09 GMT
Eek.  Ugly trace.  Using your mix of phx hadoop and hbase, can you test
successfully without CDH?
On Jun 13, 2014 1:11 AM, "Seonghwan Moon" <sofangel@gmail.com> wrote:

> Hello Stan,
>
> I have tried but failed  with (CDH5.0.1_hadoop2.3.0 + HBase 0.98.1 + PHX 4
> )
>
> Here is the error messages.
> Any idea?
>
> 14/06/13 17:10:17 WARN ipc.CoprocessorRpcChannel: Call failed on
> IOException
> org.apache.hadoop.hbase.client.RetriesExhaustedException: Failed after
> attempts=35, exceptions:
> Fri Jun 13 17:01:06 KST 2014,
> org.apache.hadoop.hbase.client.RpcRetryingCaller@62d99734,
> java.io.IOException: java.io.IOException: For input string: "1_CDH5"
>         at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2051)
>         at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:98)
>         at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.consumerLoop(SimpleRpcScheduler.java:160)
>         at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler.access$000(SimpleRpcScheduler.java:38)
>         at
> org.apache.hadoop.hbase.ipc.SimpleRpcScheduler$1.run(SimpleRpcScheduler.java:110)
>         at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NumberFormatException: For input string: "1_CDH5"
>         at
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
>         at java.lang.Integer.parseInt(Integer.java:492)
>         at java.lang.Integer.parseInt(Integer.java:527)
>         at
> org.apache.phoenix.hbase.index.util.VersionUtil.encodeVersion(VersionUtil.java:37)
>         at
> org.apache.phoenix.hbase.index.util.VersionUtil.encodeVersion(VersionUtil.java:28)
>         at
> org.apache.phoenix.util.MetaDataUtil.encodeHBaseAndPhoenixVersions(MetaDataUtil.java:106)
>         at
> org.apache.phoenix.coprocessor.MetaDataEndpointImpl.getVersion(MetaDataEndpointImpl.java:1374)
>         at
> org.apache.phoenix.coprocessor.generated.MetaDataProtos$MetaDataService.callMethod(MetaDataProtos.java:6611)
>         at
> org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5493)
>         at
> org.apache.hadoop.hbase.regionserver.HRegionServer.execServiceOnRegion(HRegionServer.java:3300)
>         at
> org.apache.hadoop.hbase.regionserver.HRegionServer.execService(HRegionServer.java:3282)
>         at
> org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29501)
>         at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2012)
>         ... 5 more
>
>
>
>
>
>
>
>
>
> 2014-04-11 5:04 GMT+09:00 Stan Campbell <stan.campbell3@gmail.com>:
>
>> Upgrading the HBase version on CDH is not as hard as it sounds.  We're
>> using CDH5 with HBase 0.98 and PHX 4.  It's enough to just replace the lib
>> jars for HBase and update the sym links.
>>
>>
>> On Thu, Apr 10, 2014 at 12:30 PM, Jeffrey Zhong <jzhong@hortonworks.com>
>> wrote:
>>
>>>
>>> Apache 4.0 can't work on HBase0.96.* line as of today, it's due to an
>>> incompatible changes(MultiVersionConsistencyControl.setThreadReadPoint is
>>> removed from hbase0.98+). I created a JIRA PHOENIX-848
>>> <https://issues.apache.org/jira/browse/PHOENIX-848> which has more
>>> details.
>>>
>>> Thanks,
>>> -Jeffrey
>>>
>>> On 4/10/14 1:44 AM, "Gabriel Reid" <gabriel.reid@gmail.com> wrote:
>>>
>>> >Hi,
>>> >
>>> >Your best bet is with Phoenix 4.0.0 (2.3.3 and 3.0.0 definitely won't
>>> >work with HBase 0.96.x).
>>> >
>>> >Phoenix 4.0.0 is built against HBase 0.98.1, which is intended to be
>>> >wire-compatible with HBase 0.96.x, although there may be some things
>>> >that don't directly work when using Phoenix 4.0.0 with HBase 0.96.x. I
>>> >just ran a minimal test here (i.e. create table, add and query data)
>>> >with Phoenix 4.0.0 and HBase 0.96 (from CDH5)  and everything worked.
>>> >
>>> >Are you certain that the phoenix jar in /usr/lib/hbase/lib are being
>>> >added to the classpath when HBase is being started up (i.e. can you
>>> >verify it based on the classpath that is printed out when starting
>>> >HBase)? Depending on your setup of CDH, just putting the phoenix jar
>>> >in that location may not be sufficient.
>>> >
>>> >- Gabriel
>>> >
>>> >
>>> >
>>> >On Thu, Apr 10, 2014 at 6:48 AM, Karavany, Ido <ido.karavany@intel.com>
>>> >wrote:
>>> >> Hi All,
>>> >>
>>> >>
>>> >>
>>> >> We are trying to install any phoenix version (2.3.3 / 3.0.0 / 4.0.0)
>>> on
>>> >>CDH
>>> >> 5 (HBase 0.96) with no success.
>>> >>
>>> >>
>>> >>
>>> >> What was done?
>>> >>
>>> >>
>>> >>
>>> >> 1.       Download binary tar
>>> >>
>>> >> 2.       Untar
>>> >>
>>> >> 3.       Copy core jar file to /usr/lib/hbase/lib
>>> >>
>>> >> 4.       Restart all hbase services
>>> >>
>>> >> 5.       Execute sqlline.py
>>> >>
>>> >>
>>> >>
>>> >> We are at the end of upgrading to CDH 5 and this is currently our only
>>> >> roadblock
>>> >>
>>> >> Can you please advise on what should be done or how can we make it
>>> work?
>>> >>
>>> >>
>>> >>
>>> >> Thanks,
>>> >>
>>> >> Ido
>>> >>
>>> >>
>>> >>
>>> >> Error messages:
>>> >>
>>> >>
>>> >>
>>> >> For 4.0.0:
>>> >>
>>> >>
>>> >>
>>> >> Error: ERROR 2006 (INT08): Incompatible jars detected between client
>>> and
>>> >> server. Ensure that phoenix.jar is put on the classpath of HBase in
>>> >>every
>>> >> region server:
>>> >>org.apache.hadoop.hbase.exceptions.UnknownProtocolException:
>>> >> No registered coprocessor service found for name MetaDataService in
>>> >>region
>>> >> SYSTEM.CATALOG,,1397104167250.b4fd3c9b08093b8b6a68f49884330890.
>>> >> (state=INT08,code=2006)
>>> >>
>>> >>
>>> >>
>>> >> For 2.3.3 / 3.0.0:
>>> >>
>>> >>
>>> >>
>>> >> phoenix Not a host:port pair: PBUF
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> Intel Electronics Ltd.
>>> >>
>>> >> This e-mail and any attachments may contain confidential material for
>>> >> the sole use of the intended recipient(s). Any review or distribution
>>> >> by others is strictly prohibited. If you are not the intended
>>> >> recipient, please contact the sender and delete all copies.
>>>
>>>
>>>
>>> --
>>> 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