Whenever a slave node fails (for example, a hardware crash) all the X100 back end processes will terminate at once, making the current transaction fail and ending the TCP session with the front end. The DBMS server becomes aware of the X100 node failure (due to the above setting and assuming the master node is not the one that failed) and it will try to restart the X100 cluster. Implicitly (if yarn.enabled is set to true) this action will go through the DbAgent component, which will handle the failover and restart the slaves-set on a reduced (or same size) set of nodes for the next SQL statement.