The heartbeat sent by master to other fe is usually read timeout now,
many log like the following:
2020-12-03 21:21:41,328 WARN 105 [Util.getResultForUrl():361] failed to get result from url: http://xxxxxxxxx:port/api/bootstrap?cluster_id=1xxxxx&token=8456a755-xxxx-4ef9-a460-1547d23fc810. Read timed out
2020-12-03 21:21:41,329 WARN 32 [HeartbeatMgr.runAfterCatalogReady():140] get bad heartbeat response: type: FRONTEND, status: BAD, msg: got exception, name: xxxxxxxxx_9010_1602645254326, queryPort: 0, rpcPort: 0, replayedJournalId: 0
So, I want to use thrift protocol instead of http protocol for master to send heartbeat to other fe to escape unstable heartbeat response, just like broker and be heartbeat