Last tested: Jan 10, 2020
Indirectly, yes -- The node's aren't keeping an eye on each other directly (they aren't pinging each other) but the scheduling engine recognizes the node failure based on the internal db's node heartbeat table and will restart/redistribute the schedule jobs accordingly.
The load balancer will stop sending front-end requests to the failed node when it fails to receive a response. The scheduler will pick up on work that has failed due to a node disappearing, and restart that work on an active node.
This content is subject to limited support.