question Re: Dependency not satisfied for release IMPALA 2 on CDH5 in Archives of Support Questions (Read Only)

Dependency not satisfied for release IMPALA 2 on CDH5

scratch28 — Fri, 16 Sep 2022 09:10:04 GMT

Tried to Deploy Impala 2

but ran into this error

Dependency not satisfied for release IMPALA(2.0.0-1.impala2.0.0.p0.1861): CDH (less than 5.0).

I am on CDH 5.2.0-1.cdh5.2.0.p0.36

This is a brand new install

Re: Dependency not satisfied for release IMPALA 2 on CDH5

cjnoyes — Thu, 16 Oct 2014 01:00:44 GMT

als had problem upgrading from 5.1.0

Re: Dependency not satisfied for release IMPALA 2 on CDH5

GautamG — Thu, 16 Oct 2014 01:40:02 GMT

cjnoyes and scratch28, could each of you please post a screenshot of the error you are seeing?

Re: Dependency not satisfied for release IMPALA 2 on CDH5

scratch28 — Thu, 16 Oct 2014 02:25:56 GMT

Sure here you go

Impala2 CDH 5.2 but check says otherwise

Re: Dependency not satisfied for release IMPALA 2 on CDH5

GautamG — Thu, 16 Oct 2014 02:54:31 GMT

I don't see a screenshot in the post, just a yellow triangle. Could you put it up on a webhost somewhere (imgur, photobucket etc) and paste a link here?

Re: Dependency not satisfied for release IMPALA 2 on CDH5

we7313 — Thu, 16 Oct 2014 14:09:18 GMT

I have the same issue as well.

Re: Dependency not satisfied for release IMPALA 2 on CDH5

Grizzly — Thu, 16 Oct 2014 14:57:48 GMT

Impala is a service included within CDH 5.x, and not a separate install from parcel. If you are running cdh 5.x then you need to add the service role within the CM UI for impala, not add it through individual parcel.

Todd

Re: Dependency not satisfied for release IMPALA 2 on CDH5

scratch28 — Thu, 16 Oct 2014 14:57:53 GMT

funny on the website forum I see the image

here is link to image

https://drive.google.com/file/d/0B0JNk6zwwqkuRUVPbF9nWVlWYmM/view?usp=sharing

Re: Dependency not satisfied for release IMPALA 2 on CDH5

eye.aquae — Fri, 17 Oct 2014 07:57:08 GMT

delete impala and re - add service

but cannot start the impalads

logs :

Internal communication is not authenticated

external communication is not authenticated

and if uncheck "Use Debug Build" ,

Catalog Server, statstore also failed to start

Service did not start successfully; not all of the required roles started: Service has only 0 Impala Daemon roles running instead of minimum required 1.

Re: Dependency not satisfied for release IMPALA 2 on CDH5

eye.aquae — Fri, 17 Oct 2014 08:54:19 GMT

excute : /opt/cloudera/parcels/CDH-5.2.0-1.cdh5.2.0.p0.36/lib/impala/sbin-debug/impalad

result:
/opt/cloudera/parcels/CDH-5.2.0-1.cdh5.2.0.p0.36/lib/impala/sbin-debug/impalad: error while loading shared libraries: libjsig.so: cannot open shared object file: No such file or directory

Re: Dependency not satisfied for release IMPALA 2 on CDH5

GautamG — Fri, 17 Oct 2014 12:01:15 GMT

Please do not run the impalad daemon directly from the command line in
that fashion. You can use Cloudera Manager to start the service and
use impala-shell to run your queries.

Re: Dependency not satisfied for release IMPALA 2 on CDH5

cjnoyes — Sat, 18 Oct 2014 21:11:15 GMT

problem solved, the parcels were extra not needed and built into cdh 5.2

Re: Dependency not satisfied for release IMPALA 2 on CDH5

eye.aquae — Mon, 20 Oct 2014 03:01:02 GMT

Did not meant to start impalad in command-line

But the problem is when impala service was added to cluster in CM UI, there is only one impalad started, others failed to start

Re: Dependency not satisfied for release IMPALA 2 on CDH5

cjnoyes — Mon, 20 Oct 2014 14:02:22 GMT

the other screen shot is the same as I saw. It turns out that I didn't need the impala parcel, it was built into cdh5.2

Re: Dependency not satisfied for release IMPALA 2 on CDH5

rube — Thu, 06 Nov 2014 05:47:11 GMT

So does that mean if I use cdh5.02,the cluster will install impala1.3,and if I use cdh5.2.0 ,impala version will be impala1.4?

and if I want to upgrade impala,should upgrade cdh first?

Re: Dependency not satisfied for release IMPALA 2 on CDH5

Darren — Thu, 06 Nov 2014 19:17:40 GMT

Impala is part of CDH 5. So to upgrade impala, you upgrade all of CDH. You don't upgrade CDH "first". That's the only step.

Be sure to follow the Cloudera Manager documentation for upgrades, as CDH5.2 has special upgrade steps.
First upgrade Cloudera Manager:
http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_ag_upgrading_cm.html

Then upgrade CDH:
http://www.cloudera.com/content/cloudera/en/documentation/core/latest/topics/cm_mc_upgrade_to_cdh52.html