Re: Workers maxing out heap, excessive GC, mk_acker_bolt->pending map is huge (0.9.5)

2015-09-01 Thread Jason Chen
Reply-To: "user@storm.apache.org<mailto:user@storm.apache.org>" Date: Friday, August 21, 2015 at 2:17 AM To: "user@storm.apache.org<mailto:user@storm.apache.org>" Subject: Re: Workers maxing out heap, excessive GC, mk_acker_bolt->pending map is huge (0.9.5) pá

Re: Workers maxing out heap, excessive GC, mk_acker_bolt->pending map is huge (0.9.5)

2015-08-26 Thread Jason Chen
catch (Throwable t) { /*nothing to recover */ } finally { collector.ack(tuple) } Hope this will fix your issue. Le 21 août 2015 02:17, "Jason Chen" mailto:jason.c...@hulu.com>> a écrit : Hi all. Here’s what I’m seeing. I’ve got a fairly simple topology, consisting of 3 bolts. Kafk

Workers maxing out heap, excessive GC, mk_acker_bolt->pending map is huge (0.9.5)

2015-08-20 Thread Jason Chen
Hi all. Here’s what I’m seeing. I’ve got a fairly simple topology, consisting of 3 bolts. Kafka spout, simple processing bolt (JSON parse to POJO, a bit of processing, and back to JSON), and Kafka Bolt (output). 12 workers, Xmx1G. It runs happily for a little over a day, then basically slow