Brokers failed repeatedly leaving behind page-cache in memory, which caused
broker restarts to fail with OOM every time.
After manually cleaning up page-cache, I was able to restart the broker.
However, still wondering what could have caused this state in the first place.
Any ideas?
-Zakee
Hi,
This is probably not a Kafka bug, but we should improve the information we
report in this case. Something along the lines of what Lucene did here:
https://issues.apache.org/jira/browse/LUCENE-5673
This error may be caused by lack of enough unfragmented virtual address
space or too restrictiv
Did you recently add topics / partitions? Each partitions takes a memory
buffer for replication, so you sometimes get OOME by adding partitions
without sizing memory.
You basically need the Java heapsize to be larger than # partitions on the
broker X replica.fetch.size
Gwen
On Wed, Dec 14, 2016
