Hi,
We have a setup with heka clients connection to a central heka master. The heka master is configured with SSL. Clients send logs to the master using TcpOutput with use_tls = true. The problem is that when the master is down, heka starts consuming 100% of one CPU on the clients. I suspect this is due to SSL retry.\ Disabling SSL **on the agents (with the master down) stops heka from fully using a CPU.
Here is a cpuprof from a client when the master was down:
Hi, We have a setup with heka clients connection to a central heka master. The heka master is configured with SSL. Clients send logs to the master using TcpOutput with use_tls = true. The problem is that when the master is down, heka starts consuming 100% of one CPU on the clients. I suspect this is due to SSL retry.\ Disabling SSL **on the agents (with the master down) stops heka from fully using a CPU.
Here is a cpuprof from a client when the master was down:
Would building heka with go 1.6 help ? I think there are some improvements to the SSL connection in the newer version.