This is an automated email from the ASF dual-hosted git repository.

msingh pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hadoop-ozone.git


The following commit(s) were added to refs/heads/master by this push:
     new c5b0ba6  HDDS-3812. Disable netty resource leak detector in datanode. 
(#1080)
c5b0ba6 is described below

commit c5b0ba6522931a548457623c16542a0c92497b2f
Author: Lokesh Jain <[email protected]>
AuthorDate: Tue Jun 16 20:10:34 2020 +0530

    HDDS-3812. Disable netty resource leak detector in datanode. (#1080)
---
 hadoop-ozone/dist/src/shell/ozone/ozone | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/hadoop-ozone/dist/src/shell/ozone/ozone 
b/hadoop-ozone/dist/src/shell/ozone/ozone
index efcb312..42e8dca 100755
--- a/hadoop-ozone/dist/src/shell/ozone/ozone
+++ b/hadoop-ozone/dist/src/shell/ozone/ozone
@@ -104,7 +104,9 @@ function ozonecmd_case
       # for disabling netty PooledByteBufAllocator thread caches for non-netty 
threads.
       # This parameter significantly reduces GC pressure for Datanode.
       # Corresponding Ratis issue 
https://issues.apache.org/jira/browse/RATIS-534.
-      HDDS_DN_OPTS="${HDDS_DN_OPTS} 
-Dlog4j.configurationFile=${HADOOP_CONF_DIR}/dn-audit-log4j2.properties 
-Dorg.apache.ratis.thirdparty.io.netty.allocator.useCacheForAllThreads=false"
+      # TODO: Fix the problem related to netty resource leak detector throwing
+      # exception as mentioned in HDDS-3812
+      
HDDS_DN_OPTS="-Dorg.apache.ratis.thirdparty.io.netty.allocator.useCacheForAllThreads=false
 -Dorg.apache.ratis.thirdparty.io.netty.leakDetection.level=disabled 
-Dlog4j.configurationFile=${HADOOP_CONF_DIR}/dn-audit-log4j2.properties 
${HDDS_DN_OPTS}"
       HADOOP_OPTS="${HADOOP_OPTS} ${HDDS_DN_OPTS}"
       HADOOP_CLASSNAME=org.apache.hadoop.ozone.HddsDatanodeService
       OZONE_RUN_ARTIFACT_NAME="hadoop-ozone-datanode"


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to