hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15683) Client.setupConnection should not block Client.stop() calls
Date Fri, 17 Aug 2018 05:41:00 GMT

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

Steve Loughran commented on HADOOP-15683:

Is this the same as HADOOP-10219? Linking to that

> Client.setupConnection should not block Client.stop() calls
> -----------------------------------------------------------
>                 Key: HADOOP-15683
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15683
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: common, ipc
>            Reporter: Lukas Majercak
>            Assignee: Lukas Majercak
>            Priority: Critical
>         Attachments: HADOOP-15683.000.patch
> If the IPC Client is still setting up connections when Client.stop() is called, the stop()
call will not succeed until setupConnection finishes (successfully or with failure). 
> This can cause very long delay (maxFailures * timeout can be more than 10minutes depending
on configuration) in stopping the client. 
> Client.stop() is for example used in NN switch from Standby to Active, and can therefore
have very bad consequences and cause downtime.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message