Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

IMPALA ASSIGNMENT LOCALITY has become bad

Highlighted

IMPALA ASSIGNMENT LOCALITY has become bad

New Contributor

Please provide the solution for below Error, i am getting error continuously 


The health test result for IMPALA_ASSIGNMENT_LOCALITY has become bad: 100.00% of assignments operating on local data over the past 30 minute(s). 12,885 local assignments. 12,885 total assignments. Time: Nov 6, 2019 5:19:50 PM 

 

1 REPLY 1

Re: IMPALA ASSIGNMENT LOCALITY has become bad

Cloudera Employee

Hi @Rahulwp,

Impala Assignment Locality check whether recent IO tasks are operating on local data. Therefore many things can cause the problem. The most simple one is that HDFS DataNodes are not co-located with the ImpalaD roles, or some roles might be stopped. The error can also appear if Impala daemons are crashing but in this case other health issues should appear as well.

However, the error message says: "bad: 100.00% of assignments operating on local data" which is the expected behavior. Based on the error message I would recommend checking:

Don't have an account?
Coming from Hortonworks? Activate your account here