Major Description
JVMPauseMonitor may be printing unexpected Error logs when GC is heavy and the cluster keeps triggering re-election.
After investigating the relevant code, it is found that the Preconditions here are unreasonable. When we update, we will first update the serverstate's term and then shutdown LeaderState. If any other thread calls leaderState's getCurrentTerm in the meantime, this will cause an error, so it's not necessary at this point
