morningman edited a comment on issue #2357: Fe will notify new FE type transfer 
and quit unexpected
   The timeline for this question is as follows:
   1. For some reason, the master have lost contact with the other two 
followers . Judging from the logs of the master, for almost 40 seconds, the 
master did not print any logs. It is suspected that it is stuck due to full gc 
or other reasons, causing the other two followers to think that the master has 
been disconnected.
   2. After the other two followers re-elected, they continued to provide 
   3. The master node is manually restarted afterwards. When restarting it for 
the first time, it needs to rollback some committed logs, so it needs to be 
closed and restarted again. After restarting again, it returns to normal.
   The main reason is that the master got stuck for 40 seconds for some reason. 
This issue requires further observation.
   At the same time, in order to alleviate this problem, we decided to set 
bdbje's heartbeat timeout as a configurable value. The default is 30 seconds. 
Can be configured to 1 minute, try to avoid this problem first.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to