Apache
/
hadoop
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HDDS-1284. Adjust default values of pipline recovery for more resilient service restart.

This commit is contained in:
Márton Elek 2019-04-12 14:09:35 +02:00
parent b067f8acaa
commit 9248b7d58b
No known key found for this signature in database
GPG Key ID: D51EA8F00EE79B28
2 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
hadoop-hdds/common/src/main/java/org/apache/hadoop/hdds/scm/ScmConfigKeys.java
View File

@ -260,7 +260,7 @@ public final class ScmConfigKeys {
public static final String OZONE_SCM_STALENODE_INTERVAL =
"ozone.scm.stale.node.interval";
public static final String OZONE_SCM_STALENODE_INTERVAL_DEFAULT =
"90s";
"5m";
public static final String OZONE_SCM_HEARTBEAT_RPC_TIMEOUT =
"ozone.scm.heartbeat.rpc-timeout";
@ -330,7 +330,7 @@ public final class ScmConfigKeys {
"ozone.scm.pipeline.destroy.timeout";
public static final String OZONE_SCM_PIPELINE_DESTROY_TIMEOUT_DEFAULT =
"300s";
"66s";
public static final String OZONE_SCM_PIPELINE_CREATION_INTERVAL =
"ozone.scm.pipeline.creation.interval";

4
hadoop-hdds/common/src/main/resources/ozone-default.xml
View File

@ -1052,7 +1052,7 @@
</property>
<property>
<name>ozone.scm.stale.node.interval</name>
<value>90s</value>
<value>5m</value>
<tag>OZONE, MANAGEMENT</tag>
<description>
The interval for stale node flagging. Please
@ -1291,7 +1291,7 @@
</property>
<property>
<name>ozone.scm.pipeline.destroy.timeout</name>
<value>300s</value>
<value>66s</value>
<tag>OZONE, SCM, PIPELINE</tag>
<description>
Once a pipeline is closed, SCM should wait for the above configured time