In some cases (like backups of VMs where ColumnStore modules run) it is normal and expected to get some module(s) non-responsive for some time. ProgMgr pings to other modules are tunable with ModuleHeartbeatPeriod and ModuleHeartbeatCount settings, but there are some timeouts that are not, for example this:

Oct 22 18:02:45 PM1-DEV joblist[8444]: 45.773757 |0|0|0| C 05 CAL0000: /data/buildbot/bb-worker/centos7/mariadb-columnstore-engine/dbcon/joblist/distributedenginecomm.cpp @ 382 DEC: lost connection to X.Y.Z.T

Please, provide a way to tune all timeouts. Ideally - with dynamic settings (so that values can be increased temporary during some maintenance period without the need to restart the enrtire system).