HDDS-1284. Adjust default values of pipline recovery for more resilient service restart. Contributed by Elek, Marton. (#608)

This commit is contained in:
Elek, Márton 2019-03-15 22:51:37 +01:00 committed by Ajay Yadav
parent 16b78622cc
commit 44b8451821
2 changed files with 4 additions and 4 deletions

View File

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

View File

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