(Service Check Timed Out) for “Check_MK” service

If you select “no IP” for an host it gets automatically the host status “assumed to be up”.
I think this is an internal setting and cannot be changed. Only overwritten by an own rule.

A timeout of the “Check MK” service on the cluster means the data from the cluster nodes is not coming in time. How long is the execution time of the Check MK service on the cluster nodes?