Reply
Cloudera Employee
Posts: 578
Registered: ‎01-20-2014

Re: Dependency not satisfied for release IMPALA 2 on CDH5

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.

Regards,
Gautam Gopalakrishnan
New Contributor
Posts: 5
Registered: ‎08-07-2014

Re: Dependency not satisfied for release IMPALA 2 on CDH5

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

New Contributor
Posts: 5
Registered: ‎08-28-2014

Re: Dependency not satisfied for release IMPALA 2 on CDH5

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

New Contributor
Posts: 5
Registered: ‎08-07-2014

Re: Dependency not satisfied for release IMPALA 2 on CDH5

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

Contributor
Posts: 78
Registered: ‎06-19-2014

Re: Dependency not satisfied for release IMPALA 2 on CDH5

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?

Highlighted
Cloudera Employee
Posts: 509
Registered: ‎07-30-2013

Re: Dependency not satisfied for release IMPALA 2 on CDH5

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