Ha.health-monitor.rpc-timeout.ms hortonworks

3980

项是:ha.health-monitor.rpc-timeout.ms,默认是50000ms,可以适当调长一些. < property> ha.health-monitor.rpc-timeout.ms  3 Jun 2019 ha.health-monitor.check-interval.ms ha.health-monitor.sleep-after-disconnect.ms ha.health-monitor.rpc-timeout.ms ha.failover-controller.new-active.rpc-timeout.ms, Default value: 60000. Default source: core-default.xml. ha.health-monitor.check-interval.ms, Default value: 1000. 项是:ha.health-monitor.rpc-timeout.ms,默认是50000ms,可以适当调长一些.

ha.health-monitor.rpc-timeout.ms: 实际 monitorHealth() 调用超时时间。 45000 ha.failover-controller.new-active.rpc-timeout.ms: FC等待新任务的超时时间,在设置时间内有新任务,即重新进入激活状态。 60000 ha.failover-controller.graceful-fence.rpc-timeout.ms: FC等待旧任务的超时时间,然后进入 dfs.journalnode.rpc-address 0.0.0.0:8485 hdfs-default.xml yarn.ipc.rpc.class org.apache.hadoop.yarn.ipc.HadoopYarnProtoRPC yarn-default.xml mapreduce.job 2016-08-25T14:12:55+08:00 https://segmentfault.com/feeds/blog/timger http://www.creativecommons.org/licenses/by-sa/2.5/rdf If you don’t want failover to happen that fast, I told him, you can simply increase ha.health-monitor.rpc-timeout.ms config key to whatever you want. Joking aside, the above is something that can help mitigate, but that would be a temporary fix rather than addressing root cause. The ZKFC property for monitorHealth RPC timeouts has been changed to be more specific, and is now called ha.health-monitor.rpc-timeout.ms. Bummer.

项是:ha.health-monitor.rpc-timeout.ms,默认是50000ms,可以适当调长一些.