If disable_sescmd_history is not combined with disable_slave_recovery option, it is possible for the session states to be in an inconsistent state across the slave nodes. It is possible that this will either cause outright errors when queries are made to a node or even possibly false data being used in a read.

The fix to this would be to always disable the recovery of slaves when the session command history is disabled.