Then the Impala Service may not start or stay running correctly, a few additional configuration changes will need to be made to get this service running. Also take a look at the Cloudera doc: Using Impala with Isilon Storage
On further review, the Impala Daemon will not stay started correctly.
The process will continue to exit post start.
On reviewing the Impalad log we see the following info and errors.
-Short-circuit reads are not enabled
-block tracking is not properly enabled because of dfs.client.file-block-storage-locations.timeout.millis timeout
In order to correct these, from Cloudera Manager search for: dfs_client_read_shortcircuit
And select the Isilon : Enable HDFS Short-Circuit Reads
Enable HDFS Short-Circuit Read on the Gateway Default Group
In HDFS Client Advanced Configuration Snippet (Safety Valve) for hdfs-site.xml and the Cluster-wide Advanced Configuration Snippet (Safety Valve) for core-site.xml properties for the Isilon service
Add a new value of the dfs.client.file-block-storage-locations.timeout.millis property to 10000
Also add In the Isilon Cluster-wide Advanced Configuration Snippet (Safety Valve) for core-site.xml property for the Isilon service
Set the value of the hadoop.security.token.service.use_ip property to FALSE.
Save and return to Cloudera Manager Dashboard, since configuration changes have been made we need to redeploy configuration and restart services.
Select, to Deploy Client Configuration
Monitor the deploy
We now need to restart the services, affected by the configuration redeployment
Restart all the services,
Monitor the restarts,
You may still see alarms on services based on prior alert triggers
The alarms can be viewed for their status,
The alarms will timeout and the status of Impala will return to healthy green.
The Impala service is now started and operational.