EM and EMCC use dynamic tables in the DB, they are updated whenever someone logs in or out and that has to replicate across the cluster. In busy systems, these tables will appear to be out of sync often but it's really just a manifestation of the dynamic nature of these. So stopping the EM service prevents updates to these and allows them to reach a quiescent state prior to the upgrade.
