For now, we will do sanity checks at the same time when updating replication peer. But this is not a safe way for procedure based replication peer modification.
For the old zk watcher way, the only thing is updating the data on zk, so if the data is updated and then we crashes, there is no problem.
For the new procedure way, we need to trigger refresh by ourselves after updating zk. If we crashes after the updating and before we record the state change of the procedure, we may fail with IllegalArgumentException when we execute the procedure next time since the data on zk has already been updated.
So the current way is to do sanity checks in PRE_PEER_MODIFICATION state, and in UPDATE_STORAGE state we will not do sanity checks any more, just update(overwrite) the peer storage.