Re: Minor GC time becomes longer and longer

2016-04-11 Thread Alexis Midon
Any experience with G1 for Kafka? I didn't get a chance to try it out. On Mon, Apr 11, 2016 at 3:31 AM Jakub Neubauer wrote: > Hi, > Did you consider G1 collector? > http://docs.oracle.com/javase/7/docs/technotes/guides/vm/G1.html > Jakub N. > > On 11.4.2016 12:08, jinhong lu wrote: > > Minor G

Re: Minor GC time becomes longer and longer

2016-04-11 Thread Alexis Midon
Why such a gigantic heap? 30G. In my experience, Kafka broker does not have to deal with long-lived objects, it's all about many small, ephemeral objects. Most of the data is kept off heap. We've been happy with 5G heap, 2G being for the new generation. The server has 8 cores and 60GB of ram. Her

Re: Minor GC time becomes longer and longer

2016-04-11 Thread Jakub Neubauer
Hi, Did you consider G1 collector? http://docs.oracle.com/javase/7/docs/technotes/guides/vm/G1.html Jakub N. On 11.4.2016 12:08, jinhong lu wrote: Minor GC time in my cluster becomes longer and longer, and broker loss session with zk: 2016-04-11T17:33:06.559+0800: 875.917: [GC2016-04-1

Re: Minor GC time becomes longer and longer

2016-04-11 Thread Jakub Neubauer
Hi, Did you consider G1 collector? http://docs.oracle.com/javase/7/docs/technotes/guides/vm/G1.html Jakub N. On 11.4.2016 12:08, jinhong lu wrote: Minor GC time in my cluster becomes longer and longer, and broker loss session with zk: 2016-04-11T17:33:06.559+0800: 875.917: [GC2016-04-1

Minor GC time becomes longer and longer

2016-04-11 Thread jinhong lu
Minor GC time in my cluster becomes longer and longer, and broker loss session with zk: 2016-04-11T17:33:06.559+0800: 875.917: [GC2016-04-11T17:33:06.559+0800: 875.917: [ParNew: 3363139K->10287K(3774912K), 0.0858010 secs] 3875141K->522289K(31037888K), 0.0860890 secs] [Times: user=1.46