Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Impala Assignment locality concerning

avatar
Explorer
Hi guys,
I'm getting this alert very often in impala. Please help
 
52.78% of assignments operating on local data over the past 15 minute(s). 95 local assignments. 180 total assignments. Warning threshold: 80.00%.
1 ACCEPTED SOLUTION

avatar
Champion

I dont kow if you have a custom trigger or a built in trigger for health test. 

Is the health test showing warning or critical or bad ? 

 

either way the test is  to find the data locality in the host .

" Make sure that Impala Daemon is co-located with a DataNode, and that the IP address of each Impala Daemon matches the IP address of its co-located DataNode" 

 

Please make sure if  you have enabled the below properties in hdfs-site.xml

 

 

<property>
    <name>dfs.client.read.shortcircuit</name>
    <value>true</value>
</property>

<property>
    <name>dfs.domain.socket.path</name>
    <value>/var/run/hdfs-sockets/dn</value>
</property>

<property>
    <name>dfs.client.file-block-storage-locations.timeout.millis</name>
    <value>10000</value>
</property>

Reference 

https://www.cloudera.com/documentation/enterprise/5-9-x/topics/impala_config_performance.html#config...

View solution in original post

1 REPLY 1

avatar
Champion

I dont kow if you have a custom trigger or a built in trigger for health test. 

Is the health test showing warning or critical or bad ? 

 

either way the test is  to find the data locality in the host .

" Make sure that Impala Daemon is co-located with a DataNode, and that the IP address of each Impala Daemon matches the IP address of its co-located DataNode" 

 

Please make sure if  you have enabled the below properties in hdfs-site.xml

 

 

<property>
    <name>dfs.client.read.shortcircuit</name>
    <value>true</value>
</property>

<property>
    <name>dfs.domain.socket.path</name>
    <value>/var/run/hdfs-sockets/dn</value>
</property>

<property>
    <name>dfs.client.file-block-storage-locations.timeout.millis</name>
    <value>10000</value>
</property>

Reference 

https://www.cloudera.com/documentation/enterprise/5-9-x/topics/impala_config_performance.html#config...