Support Questions

Find answers, ask questions, and share your expertise

Dependency not satisfied for release IMPALA 2 on CDH5

avatar
Contributor

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 

1 ACCEPTED SOLUTION

avatar
Master Collaborator

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

View solution in original post

15 REPLIES 15

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

avatar
Explorer

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

avatar
Contributor

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?

avatar
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....

avatar
Contributor

funny on the website forum I see the image

here is link to image

 

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

 

avatar
Explorer

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