From b39e9efeeb55a543ccb472b4e800a93de5aac5a1 Mon Sep 17 00:00:00 2001
From: Arpit Agarwal <arp@apache.org>
Date: Tue, 26 Apr 2016 20:46:38 -0700
Subject: [PATCH] HADOOP-13039. Add documentation for configuration property
 ipc.maximum.data.length (Contributed by Mingliang Liu)

---
 .../hadoop-common/src/main/resources/core-default.xml | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml b/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
index 51e2df48317..d2380479747 100644
--- a/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
+++ b/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
@@ -1085,6 +1085,17 @@
     </description>
 </property>
 
+<property>
+  <name>ipc.maximum.data.length</name>
+  <value>67108864</value>
+  <description>This indicates the maximum IPC message length (bytes) that can be
+    accepted by the server. Messages larger than this value are rejected by
+    server immediately. This setting should rarely need to be changed. It merits
+    investigating whether the cause of long RPC messages can be fixed instead,
+    e.g. by splitting into smaller messages.
+  </description>
+</property>
+
 <!-- Proxy Configuration -->
 
 <property>