[
https://issues.apache.org/jira/browse/HADOOP-13039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15256798#comment-15256798
]
Hadoop QA commented on HADOOP-13039:
------------------------------------
| (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} docker {color} | {color:red} 0m 3s {color}
| {color:red} Docker failed to build yetus/hadoop:fbe3e86. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12800588/HADOOP-13039.001.patch
|
| JIRA Issue | HADOOP-13039 |
| Console output |
https://builds.apache.org/job/PreCommit-HADOOP-Build/9171/console |
| Powered by | Apache Yetus 0.2.0 http://yetus.apache.org |
This message was automatically generated.
> Add documentation for configuration property ipc.maximum.data.length for
> controlling maximum RPC message size.
> --------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-13039
> URL: https://issues.apache.org/jira/browse/HADOOP-13039
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Reporter: Chris Nauroth
> Assignee: Mingliang Liu
> Attachments: HADOOP-13039.000.patch, HADOOP-13039.001.patch,
> HADOOP-13039.001.patch
>
>
> The RPC server enforces a maximum length on incoming messages. Messages
> larger than the maximum are rejected immediately as potentially malicious.
> The maximum length can be tuned by setting configuration property
> {{ipc.maximum.data.length}}, but this is not documented in core-site.xml.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
