Dependency not satisfied for release IMPALA 2 on CDH5

[#1]

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 

[#2]

als had problem upgrading from 5.1.0

[#3]

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

[#4]

Sure here you go

Impala2 CDH 5.2 but check says otherwise

[#5]

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?

[#6]

I have the same issue as well.

[#7 · Accepted solution]

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

[#8]

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.

[#9]

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

[#10]

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.