# Frequently young gc: is memory leak in elastic 2.3.0? **URL:** \ **Category:** Elasticsearch\ **Created:** [August 18, 2016, 7:11am UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320 "2016-08-18T07:11:58Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![walker](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@walker](https://discuss.elastic.co/u/walker)\ **Post date:** [August 18, 2016, 7:11am UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320/1 "2016-08-18T07:11:58Z")
the jvm parameters is : ![](https://us1.discourse-cdn.com/elastic/original/2X/d/d6f8f29ca5b7d8e54d1d230706d0d96a2328d1ef.png) the text is: /usr/java/jdk1.7.0\_79/bin/java -Xms32g -Xmx32g -Xmn12g -Djava.awt.headless=true -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+HeapDumpOnOutOfMemoryError -XX:+DisableExplicitGC -Dfile.encoding=UTF-8 -Djna.nosys=true -Des.path.home=/data/soft/elasticsearch\_goods -cp /data/soft/elasticsearch\_goods/lib/elasticsearch-2.3.0.jar:/data/soft/elasticsearch\_goods/lib/\* org.elasticsearch.bootstrap.Elasticsearch start -d --security.manager.enabled false and found young gc in the logs: ![](https://us1.discourse-cdn.com/elastic/original/2X/c/cf6b8d8dbdc5868bac662a85361214ca8233ece6.png) the text show: 156802 [2016-08-18 15:18:21,528][INFO][monitor.jvm] [es\_192.168.16.240] [gc][young][2492643][39653] duration [753ms], collections [1]/[1.1s], total [753ms]/[6.3h], memory [14.9gb]-\>[5.7gb]/[30.8gb], all\_pools {[young] [9.3gb]-\>[57.4mb]/[9.6gb]}{[survivor] [110.3mb]-\>[253.4mb]/[1.1gb]}{[old] [5.4gb]-\>[5.4gb]/[20gb]} 156803 [2016-08-18 15:18:30,855][INFO][monitor.jvm] [es\_192.168.16.240] [gc][young][2492652][39654] duration [734ms], collections [1]/[1.3s], total [734ms]/[6.3h], memory [14.8gb]-\>[5.7gb]/[30.8gb], all\_pools {[young] [9.1gb]-\>[48.9mb]/[9.6gb]}{[survivor] [253.4mb]-\>[229.3mb]/[1.1gb]}{[old] [5.4gb]-\>[5.4gb]/[20gb]} 156804 [2016-08-18 15:18:40,271][INFO][monitor.jvm] [es\_192.168.16.240] [gc][young][2492661][39655] duration [737ms], collections [1]/[1.4s], total [737ms]/[6.3h], memory [14.6gb]-\>[5.6gb]/[30.8gb], all\_pools {[young] [9gb]-\>[48.4mb]/[9.6gb]}{[survivor] [229.3mb]-\>[144.4mb]/[1.1gb]}{[old] [5.4gb]-\>[5.4gb]/[20gb]} 156805 [2016-08-18 15:18:49,966][INFO][monitor.jvm] [es\_192.168.16.240] [gc][young][2492670][39656] duration [735ms], collections [1]/[1.6s], total [735ms]/[6.3h], memory [13.9gb]-\>[5.6gb]/[30.8gb], all\_pools {[young] [8.4gb]-\>[55.7mb]/[9.6gb]}{[survivor] [144.4mb]-\>[133.4mb]/[1.1gb]}{[old] [5.4gb]-\>[5.4gb]/[20gb]} 156806 [2016-08-18 15:19:01,989][INFO][monitor.jvm] [es\_192.168.16.240] [gc][young][2492682][39657] duration [766ms], collections [1]/[1s], total [766ms]/[6.3h], memory [14.7gb]-\>[5.7gb]/[30.8gb], all\_pools {[young] [9.1gb]-\>[132.8mb]/[9.6gb]}{[survivor] [133.4mb]-\>[187.7mb]/[1.1gb]}{[old] [5.4gb]-\>[5.4gb]/[20gb]} 156807 [2016-08-18 15:19:11,579][INFO][monitor.jvm] [es\_192.168.16.240] [gc][young][2492691][39658] duration [730ms], collections [1]/[1.5s], total [730ms]/[6.3h], memory [14.9gb]-\>[5.6gb]/[30.8gb], all\_pools {[young] [9.3gb]-\>[40.6mb]/[9.6gb]}{[survivor] [187.7mb]-\>[148.7mb]/[1.1gb]}{[old] [5.4gb]-\>[5.4gb]/[20gb]} 156973 [2016-08-18 15:19:21,784][INFO][monitor.jvm] [es\_192.168.16.240] [gc][young][2492701][39659] duration [733ms], collections [1]/[1.1s], total [733ms]/[6.3h], memory [1 is there anybody encounter this problem? ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 18, 2016, 8:55am UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320/2 "2016-08-18T08:55:33Z")
Please don't post pictures of text, they are difficult to read and some people may not be even able to see them.. ---
**Author:** ![walker](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@walker](https://discuss.elastic.co/u/walker)\ **Post date:** [August 19, 2016, 1:20am UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320/3 "2016-08-19T01:20:48Z")
thanks, I have update my post. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [August 19, 2016, 1:24am UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320/4 "2016-08-19T01:24:34Z")
Lots of young GC is expected, is it causing issues? Why do you think it's a leak? ---
**Author:** ![walker](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@walker](https://discuss.elastic.co/u/walker)\ **Post date:** [August 19, 2016, 1:48am UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320/5 "2016-08-19T01:48:33Z")
yes, problem happens during these young GC, although these young GC looks pretty qucikly. the problems is: the read time out exception increase obviously during young GC, the exception are as follows: java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:152) at java.net.SocketInputStream.read(SocketInputStream.java:122) at org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:139) at org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:155) at org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:284) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:140) at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:57) at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:261) at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:165) at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:167) at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:272) at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:271) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107) at io.searchbox.client.http.JestHttpClient.executeRequest(JestHttpClient.java:109) at io.searchbox.client.http.JestHttpClient.execute(JestHttpClient.java:56) In my point of view, occasionally young GC is harmless, but so frequently young GC(5-10 seconds interval) may do have bad effect, because Both the young- and old-generation garbage collectors have phases that "stop the world." ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [August 19, 2016, 8:56am UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320/6 "2016-08-19T08:56:08Z")
Sometimes, the best way to have faster garbage collections is to give less memory to the JVM. ---
**Author:** ![walker](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@walker](https://discuss.elastic.co/u/walker)\ **Post date:** [August 20, 2016, 9:04am UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320/7 "2016-08-20T09:04:21Z")
thanks, but what do you mean by saying that ? is 32g heap size to large? or is 12g young generation size too large? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 10:26pm UTC](https://discuss.elastic.co/t/frequently-young-gc-is-memory-leak-in-elastic-2-3-0/58320/8 "2017-07-05T22:26:26Z")