[ 
https://issues.apache.org/jira/browse/HADOOP-7221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028030#comment-13028030
 ] 

ramkrishna.s.vasudevan commented on HADOOP-7221:
------------------------------------------------

The problem was whenever network was unplugged the read operation was getting a 
timedout exception and it was trying again. This continued for almost 15 times 
and only then some connectionloss exception came and could come out.
By this time it was taking around 45 mins.
Hence we have done something like, configure the parameter 
"max.ping.retries.on.socket.timeout" to a value where you can configure a value 
after which it should come out after getting a socket time.  So while retrying 
chk for this configured value and once reached come out.

This problem comes only in unplug scenarios.  So based on the scenario this 
value can be configured as to when how much time it should chk to get a 
connection.

> When Namenode network is unplugged, DFSClient operations waits for ever
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-7221
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7221
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc
>            Reporter: Uma Maheswara Rao G
>
> When NN/DN is shutdown gracefully, the DFSClient operations which are waiting 
> for a response from NN/DN, will throw exception & come out quickly
> But when the NN/DN network is unplugged, the DFSClient operations which are 
> waiting for a response from NN/DN, waits for ever.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to