Open arthur-xie opened 7 years ago
Hi. Yes, this is a known problem. Can you mention all the steps to reproduce the problem? I would like to write a test on this as i don't have any replica set right now.
Any update on this?
I am having the same issue - Steps to reproduce.
top
on the machine with erlang mqtt driver running. You'll see beam.smp on top consuming high CPU.
When we shutdown one node of a replica set, the beam process consumes about 120%(multiple cores) CPU. After some debugging, we found when any node down, the mc_monitor:check will crash on line
{ok, Conn} = mc_worker_api:connect(ConnectArgs)
because of unmatch between{error, econnrefused}
and{ok, Conn}
. This will make mc_monitor step into dead loop(no sleep because the Type is unknown).