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.

As far as I know, TarsGo supports registering client filter with tars.RegisterClientFilter() method.
And if you have multiple client filter, you may have to use tars.RegisterPreClientFilter and tars.RegisterPostClientFilter.

However, I don't want to split any of them to one pre filter and one post filter when I register multiple client filters.

For example, I register client breaker