From 92548e09c68edb82dffb5bdcd2ebc1e3ea4cb4bc Mon Sep 17 00:00:00 2001 From: Arpit Agarwal 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 96bac4d4aff..85c1f0d76f4 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 @@ -1012,6 +1012,17 @@ for ldap providers in the same way as above does. + + ipc.maximum.data.length + 67108864 + 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. + + +