hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14035) Reduce fair call queue backoff's impact on clients
Date Mon, 05 Jun 2017 14:49:04 GMT

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

Daryn Sharp commented on HADOOP-14035:
--------------------------------------

None of the findbugs warnings are applicable to this patch, nor is the sftp test failure.

> Reduce fair call queue backoff's impact on clients
> --------------------------------------------------
>
>                 Key: HADOOP-14035
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14035
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc
>    Affects Versions: 2.7.0
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>         Attachments: HADOOP-14035.patch
>
>
> When fcq backoff is enabled and an abusive client overflows the call queue, its connection
is closed, as well as subsequent good client connections.   Disconnects are very disruptive,
esp. to multi-threaded clients with multiple outstanding requests, or clients w/o a retry
proxy (ex. datanodes).
> Until the abusive user is downgraded to a lower priority queue, disconnect/reconnect
mayhem occurs which significantly degrades performance.  Server metrics look good despite
horrible client latency.
> The fcq should utilize selective ipc disconnects to avoid pushback disconnecting good
clients.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message