hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-12903) IPC Server should allow suppressing exception logging by type, not log 'server too busy' messages
Date Wed, 09 Mar 2016 00:08:40 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arpit Agarwal updated HADOOP-12903:
-----------------------------------
    Attachment: HADOOP-12903.03.patch

Thanks [~cnauroth], v3 patch addresses your comment. I missed your comment earlier in the
jira noise.

> 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
>         Attachments: HADOOP-12903.01.patch, HADOOP-12903.02.patch, HADOOP-12903.03.patch
>
>
> 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.
> The IPC Server should also allow services to skip logging certain exception types altogether.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message