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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2016/03/08 00:39:40 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=15184031#comment-15184031 ] 

Hadoop QA commented on HADOOP-12903:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m 0s {color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s {color} | {color:red} HADOOP-12903 does not apply to trunk. Rebase required? Wrong Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL | https://issues.apache.org/jira/secure/attachment/12791863/HADOOP-12903.01.patch |
| JIRA Issue | HADOOP-12903 |
| Console output | https://builds.apache.org/job/PreCommit-HADOOP-Build/8811/console |
| Powered by | Apache Yetus 0.3.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> 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-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)