I think its the path you have, but add a lib at the end /opt/cloudera/parcels/CDH-5.3.1-1.cdh5.3.1.p0.5/lib/hbase/lib
On Fri, Feb 27, 2015 at 12:15 PM, Brady, John <john.br...@intel.com> wrote: > Anil, > > > > I would also like to know the name of the configuration in Cloudera > Manager? Thanks. > > > > Also are you aware of the issue on AWS where internal and external IPs > gett confused and zookeeper can’t connect to HBase properly? > > > > The solution posted below doesn’t work for cloudera clusters as it > involves modifying config files on the sever which breaks cloudera. > > > > http://mail-archives.apache.org/mod_mbox/phoenix-user/201502.mbox/browser > > > > Thanks > > > > > > *From:* Kevin Verhoeven [mailto:kevin.verhoe...@ds-iq.com] > *Sent:* Friday, February 27, 2015 5:08 PM > > *To:* user@phoenix.apache.org > *Subject:* RE: installing Phoenix on a Cloudera 5.3.1 cluster > > > > Anil, > > > > Do you know the name of the configuration in Cloudera Manager where I can > add a folder in the classpath of HBase? I’d like to use this configuration > because every time I update CDH the jar is deleted. > > > > Kevin > > > > *From:* Brady, John [mailto:john.br...@intel.com <john.br...@intel.com>] > *Sent:* Friday, February 27, 2015 8:31 AM > *To:* user@phoenix.apache.org > *Subject:* RE: installing Phoenix on a Cloudera 5.3.1 cluster > > > > Ok thanks Anil. > > > > John > > > > > > *From:* anil gupta [mailto:anilgupt...@gmail.com <anilgupt...@gmail.com>] > *Sent:* Friday, February 27, 2015 3:45 PM > *To:* user@phoenix.apache.org > *Subject:* Re: installing Phoenix on a Cloudera 5.3.1 cluster > > > > Hi Job, > You need to put the server jars. IMO, it s not a good practice to put > non-cdh jars in lib folders of hbase because that jar might get wiped off > when a cdh upgrade happens. You can add a folder in classpath of hbase from > cloudera manager. In this way your custom jars will not get wiped off > during upgrade. > > Thanks, > > Anil Gupta > > > > On Fri, Feb 27, 2015 at 3:55 AM, Brady, John <john.br...@intel.com> wrote: > > Thanks, > > > > Which jars exactly? The client jar, the server jar and the core jar? All > in /opt/cloudera/parcels/CDH-5.3.1-1.cdh5.3.1.p0.5/lib/hbase > > > > Thanks > > > > > > > > *From:* Job Thomas [mailto:j...@suntecgroup.com] > *Sent:* Friday, February 27, 2015 11:48 AM > *To:* user@phoenix.apache.org; user@phoenix.apache.org > *Subject:* RE: installing Phoenix on a Cloudera 5.3.1 cluster > > > > Yes, As error says, you need to put Phoenix jar in all HBase region > servers class path. > > > > Thanks & Regards > > > > Job M Thomas*|* Platform & Technology > > SunTec Business Solutions Pvt. Ltd > > Mob : 7560885748 > > > ------------------------------ > > *From:* Brady, John [mailto:john.br...@intel.com <john.br...@intel.com>] > *Sent:* Fri 2/27/2015 5:13 PM > *To:* user@phoenix.apache.org > *Subject:* installing Phoenix on a Cloudera 5.3.1 cluster > > Hi, > > > > I’m installing Phoenix on a Cloudera 5.3.1 cluster. > > > > Which jars to I copy to the directory: > /opt/cloudera/parcels/CDH-5.3.1-1.cdh5.3.1.p0.5/lib/hbase > > > > Is it just the phoenix-4.3.0-server.jar? > > > > I did this on each server but I’m getting this error. > > > > 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,,1425031594649.2d387efde9428a05a015cca95477a911. > > at > org.apache.hadoop.hbase.regionserver.HRegion.execService(HRegion.java:5662) > > at > org.apache.hadoop.hbase.regionserver.HRegionServer.execServiceOnRegion(HRegionServer.java:3421) > > at > org.apache.hadoop.hbase.regionserver.HRegionServer.execService(HRegionServer.java:3403) > > at > org.apache.hadoop.hbase.protobuf.generated.ClientProtos$ClientService$2.callBlockingMethod(ClientProtos.java:29929) > > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2031) > > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:108) > > at > org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop(RpcExecutor.java:116) > > at > org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:96) > > at java.lang.Thread.run(Thread.java:745) (state=INT08,code=2006) > > > > Thanks > > > > ------------------------------------------------------------- > Intel Ireland Limited (Branch) > Collinstown Industrial Park, Leixlip, County Kildare, Ireland > Registered Number: E902934 > > 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. > > ------------------------------------------------------------- > Intel Ireland Limited (Branch) > Collinstown Industrial Park, Leixlip, County Kildare, Ireland > Registered Number: E902934 > > 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. > > > > > -- > > Thanks & Regards, > Anil Gupta > > ------------------------------------------------------------- > Intel Ireland Limited (Branch) > Collinstown Industrial Park, Leixlip, County Kildare, Ireland > Registered Number: E902934 > > 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. > > ------------------------------------------------------------- > Intel Ireland Limited (Branch) > Collinstown Industrial Park, Leixlip, County Kildare, Ireland > Registered Number: E902934 > > 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. >
