I have a single broker in a cluster of 9 brokers that has a
log-flush-time-99th of 260 ms or more. Other brokers have
a log-flush-time-99th of less than 30 ms. The misbehaving broker is running
on the same kind of machine (c3.4x on Ec2) that the other ones are running
on. It's bytes-in, bytes-out, and messages-in metrics are no more than any
other broker.

I am trying to rule out other factors before settling on the "bad box"
explanation. Can any one suggest other metrics I can look at to tell
whether there might be causes (other than bad node) that could explain the
higher log flush times?

Thanks!

Reply via email to