Tools / Apache HertzBeat Interview Questions
Why does HertzBeat use Netty for manager-collector communication?
The hertzbeat-remoting module builds manager-collector communication on Netty, a high-performance asynchronous networking framework, rather than plain blocking HTTP request/response calls.
Netty gives HertzBeat persistent, bidirectional connections between the manager and each collector, so task dispatch and heartbeat signaling don't need to open a new connection for every exchange. This matters as the collector fleet grows: async, non-blocking I/O means a manager node can maintain communication with far more collectors concurrently than a thread-per-connection blocking model would allow, which is a big part of why HertzBeat's collector clusters can scale horizontally without the manager becoming the bottleneck.
Manager-collector communication is built on:
Netty's async, non-blocking model mainly helps HertzBeat by:
More Related questions...
