Github user danny0405 commented on a diff in the pull request:
--- Diff: conf/defaults.yaml ---
@@ -182,7 +195,7 @@ worker.log.level.reset.poll.secs: 30
# control how many worker receiver threads we need per worker
--- End diff --
Actually task.heartbeat.frequency.secs is now only used as a metrics
reporting interval, so it can totally be longer, RPC heartbeat reporting
interval is configured by Config.WORKER_HEARTBEAT_FREQUENCY_SECS.
Because now we still use ZK as a storage of our metrics, one nimute
interval is ok in production which is the internal metrics
consumtion/aggregation time interval.