Reply
Explorer
Posts: 33
Registered: ‎07-27-2015

Dameon concerning health : Impala dameon ready health check

Hi Experts,

 

I have installed impala in 10 node cluster with 6 daemons. Catelog server and State store health is healthy.

All daemons are concerning and showing "Impala Daemon Ready Check" and "The readiness of the Impala Daemon to process queries is not known. "

 

I checked the error details and cloudera advice is

 

Advice

This is an Impala Daemon health test that checks if the Impala Daemon is ready to process queries. This check usually fails if the YARN Node Manager is not available. If the YARN Node Manager goes offline, no resources can be acquired and new queries cannot be run.

This test can be configured using the Impala Daemon Ready Status Health Check and Impala Daemon Ready Status Startup Tolerance impalad monitoring settings.

 

I verified, all node managers are healthy and able to process MR jobs.

How can i trubleshoot this error? I tried by removing and reinstalling hive and impala but it didnt work.

 

Did anyone face this issue? Can please someone help me out.

 

Any help is appreciated.

Explorer
Posts: 33
Registered: ‎07-27-2015

Re: Dameon concerning health : Impala dameon ready health check

I am still not able to crack it.
UDF queries are failing where as simple queries like hive external table is running with slow performance.

Can please anyone suggest anything.
New Contributor
Posts: 4
Registered: ‎07-30-2015

Re: Dameon concerning health : Impala dameon ready health check

I also have the same warning on 3 hosts?

No idea how to fix it
Explorer
Posts: 33
Registered: ‎07-27-2015

Re: Dameon concerning health : Impala dameon ready health check

I dont know how it get fixed.

 

But i stopped service and started after long time. Now no issues with the daemons.

 

Strange or Luck :)

Highlighted
New Contributor
Posts: 1
Registered: ‎08-14-2017

Re: Dameon concerning health : Impala dameon ready health check

I too had this issue and devs werent able to submit the query. Please respond for a solution.

 

Restart cannot be a solution though it solved the problem.

 

Anyone guys?

Announcements