HealthCheckThread is replaced by StartHealthCheck function in socket.cpp, but some of the docs/comments are not modified correspondingly. There are 3 files that HealthCheckThread is involved in:

• test/brpc_socket_unittest.cpp(3 occurrences)
• docs/cn/load_balancing.md(1 occurrence)
• src/brpc/socket.h(1 occurrence)

All sentences with 'HealthCheckThread' should be rewritten to sync with the

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

Netty's event loop threads are spawned lazily, i.e. they are created on the first task is scheduled on. A user sometimes wants to ensure the event loop threads are started when the server starts up.

We experienced a problem due to fd leak on server side. Here is the detail:

• When client send requests with packet size greater than MaxPackageLength which result in a PACKAGE_ERROR on server side
• Server close the connection by calling (*net.TCPConn).Close()
• But the connection is NOT closed since we make a copy of the underlying fd in (*transport.tcpHandler).Handle
• All subsequ