Reply
Explorer
Posts: 6
Registered: ‎05-21-2014

Impala service does not start

hi,

i have a host that i added to an existing (new cluster). i added hdfs, hbase, and hive gateway roles on it. in addition, i added impalad on it.

the impalad role fails to start. i get teh following error and was hoping someone has some clues as to how to resolve.

==

I0523 10:10:59.315976 10489 status.cc:44] ERROR: short-circuit local reads is disabled because
- Impala cannot read or execute the parent directory of dfs.domain.socket.path

@ 0x70745d (unknown)
@ 0x8f341f (unknown)
@ 0x89fa89 (unknown)
@ 0x8a14bf (unknown)
@ 0x6ec89d (unknown)
@ 0x3e4e41ed1d (unknown)
@ 0x6ec599 (unknown)
E0523 10:10:59.315994 10489 impala-server.cc:208] ERROR: short-circuit local reads is disabled because
- Impala cannot read or execute the parent directory of dfs.domain.socket.path
E0523 10:10:59.316138 10489 impala-server.cc:210] Aborting Impala Server startup due to improper configuration

==

thanks in advance for any help!

 

 

Posts: 416
Topics: 51
Kudos: 86
Solutions: 49
Registered: ‎06-26-2013

Re: Impala service does not start

@terryt I have moved this thread to the HDFS board, because I believe the setting you are having trouble with is set in your HDFS configurations.  When the datanodes start up, they create a UNIX Domain socket in the location specified by the property dfs.domain.socket.path and that socket is used for faster reads by other services.  It looks like you've got Impala set up to try to use Short Circuit Reads, but maybe HDFS is not?  Therefore the socket is not being created yet Impalad is trying to access it?

 

I believe this doc will help.

 

Clint

Explorer
Posts: 6
Registered: ‎05-21-2014

Re: Impala service does not start

Hi Clint,

thanks for your quick response and thanks for the link on post installation config. this is what i modified in cloudera manager:

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

<property>
<name>dfs.domain.socket.path</name>
<value>/var/run/hadoop-hdfs/dn._PORT</value> ----> in cloudera manager, i left it at dn instead of dn.PORT
</property>

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

 

i think cp'd the following config files to each of the impala nodes.

cp /etc/hadoop/conf/core-site.xml /etc/impala/conf

cp /etc/hadoop/conf/hdfs-site.xml /etc/impala/conf

 

after restarting the cluster, i am still getting the same error on the new host.

 

--

0527 14:59:19.056370  1084 status.cc:44] ERROR: short-circuit local reads is disabled because
  - Impala cannot read or execute the parent directory of dfs.domain.socket.path

    @           0x70745d  (unknown)
    @           0x8f341f  (unknown)
    @           0x89fa89  (unknown)
    @           0x8a14bf  (unknown)
    @           0x6ec89d  (unknown)
    @       0x3e4e41ed1d  (unknown)
    @           0x6ec599  (unknown)
E0527 14:59:19.056391  1084 impala-server.cc:208] ERROR: short-circuit local reads is disabled because
  - Impala cannot read or execute the parent directory of dfs.domain.socket.path
E0527 14:59:19.056545  1084 impala-server.cc:210] Aborting Impala Server startup due to improper configuration

thanks again in advance for your help!

terry

Explorer
Posts: 12
Registered: ‎09-25-2014

Re: Impala service does not start

Did you find the solution to your problem? I am facing the same issue.

Announcements