You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Arpit Agarwal (JIRA)" <ji...@apache.org> on 2016/03/08 00:16:41 UTC
[jira] [Updated] (HADOOP-12903) IPC Server should allow suppressing
exception logging by type, not log 'server too busy' messages
[ https://issues.apache.org/jira/browse/HADOOP-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HADOOP-12903:
-----------------------------------
Summary: IPC Server should allow suppressing exception logging by type, not log 'server too busy' messages (was: Add IPC Server support for suppressing exceptions by type, suppress 'server too busy' messages)
> IPC Server should allow suppressing exception logging by type, not log 'server too busy' messages
> -------------------------------------------------------------------------------------------------
>
> Key: HADOOP-12903
> URL: https://issues.apache.org/jira/browse/HADOOP-12903
> Project: Hadoop Common
> Issue Type: Bug
> Components: ipc
> Affects Versions: 2.7.2
> Reporter: Arpit Agarwal
> Assignee: Arpit Agarwal
>
> HADOOP-10597 added support for RPC congestion control by sending retriable 'server too busy' exceptions to clients.
> However every backoff results in a log message. We've seen these log messages slow down the NameNode.
> {code}
> 2016-03-07 15:02:23,272 INFO org.apache.hadoop.ipc.Server: Socket Reader #1 for port 8020: readAndProcess from client 127.0.0.1 threw exception [org.apache.hadoop.ipc.RetriableException: Server is too busy.]
> {code}
> We already have a metric that tracks the number of backoff events. This log message adds nothing useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)