Firstly, this error on the Samza side needs to LOG the exact underlying error (instead of wrapping it up in a SamzaException). I will log a ticket for that.
There are may several causes/symptoms to an OOM error including but not limited to: GC time limits, heap exceeded, running out of native memory or memory leaks. Can you try increasing the heap memory? (For example: Set -Xmx5g in your task.opts and set yarn.container.memory.mb > 5G). https://samza.apache.org/learn/documentation/0.10/jobs/configuration-table.html On Sun, Dec 4, 2016 at 8:20 PM, Shekar Tippur <ctip...@gmail.com> wrote: > Samza yarn application container is getting killed due to out of memory > error. > Wondering of you guys can give me some pointers on how to troubleshoot this > error. > Background: I had to change the Kafka log location and restart kafka. There > is no change in application or yarn configuration. > > org.apache.samza.SamzaException: Got out of memory error in broker proxy > thread. > > at > org.apache.samza.system.kafka.BrokerProxy$$anon$1.run( > BrokerProxy.scala:132) > > at java.lang.Thread.run(Thread.java:745) > > - Shekar > -- Jagadish V, Graduate Student, Department of Computer Science, Stanford University
