It turned out it was een over-provisioned VM. It was eventually solved by
moving the VM to another cluster. He was also not a little slow but
something in the magnitude of 100 times slower. We are now looking for some
metrics to watch and alert in case it gets slow.
On Fri, Sep 16, 2016 at 4:41 PM
To remediate, you could start another broker, rebalance, and then shut down the
busted broker. But, you really should put some monitoring on your system (to
help diagnose the actual problem). Datadog has a pretty good set of articles
for using jmx to do this:
https://www.datadoghq.com/blog/mo
