Hello, Ratis community I would like to understand the rationale behind a specific design detail of JvmPauseMonitor. In the current code base, when JvmPauseMonitor observes a JVM pause lasting over 60 seconds, it closes the RaftServerProxy in the handleJvmPause.
In our production system, some users may stop the virtual machine running the process for several minutes. When they resume the virtual machine, they find that the RaftServerProxy's state is already Closed, and they must restart it to restore the correct state. This has caused operational challenges for us. I would like to know the specific reasons for this design. What problem is it meant to prevent? If there's no particular reason, we will consider adjusting the rpcSlownessTimeout to infinity in IoTDB to disable this feature. Thanks ------------------------ Xinyu Tan
