This is an automated email from the ASF dual-hosted git repository. elek pushed a commit to branch HDDS-1469 in repository https://gitbox.apache.org/repos/asf/hadoop.git
commit 64ff28fb1dc404f2c8fca1fa9b006767cf22f232 Author: Márton Elek <[email protected]> AuthorDate: Fri Apr 26 12:14:31 2019 +0200 reestore ozone.scm.heartbeat.thread.interval --- .../common/src/main/resources/ozone-default.xml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/hadoop-hdds/common/src/main/resources/ozone-default.xml b/hadoop-hdds/common/src/main/resources/ozone-default.xml index 1dcbdc5..05bd7fe 100644 --- a/hadoop-hdds/common/src/main/resources/ozone-default.xml +++ b/hadoop-hdds/common/src/main/resources/ozone-default.xml @@ -961,7 +961,25 @@ Timeout value for the RPC from Datanode to SCM. </description> </property> + <property> + <name>ozone.scm.heartbeat.thread.interval</name> + <value>3s</value> + <tag>OZONE, MANAGEMENT</tag> + <description> + When a heartbeat from the data node arrives on SCM, It is queued for + processing with the time stamp of when the heartbeat arrived. There is a + heartbeat processing thread inside SCM that runs at a specified interval. + This value controls how frequently this thread is run. + There are some assumptions build into SCM such as this value should allow + the heartbeat processing thread to run at least three times more + frequently than heartbeats and at least five times more than stale node + detection time. If you specify a wrong value, SCM will gracefully refuse + to run. For more info look at the node manager tests in SCM. + + In short, you don't need to change this. + </description> + </property> <property> <name>ozone.scm.http-address</name> <value>0.0.0.0:9876</value> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
