# Restarting ES Service frequently for Memory Issue **URL:** \ **Category:** Elasticsearch\ **Created:** [February 28, 2011, 8:35pm UTC](https://discuss.elastic.co/t/restarting-es-service-frequently-for-memory-issue/3997 "2011-02-28T20:35:44Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Jagmee](https://avatars.discourse-cdn.com/v4/letter/j/ecd19e/32.png) [@Jagmee](https://discuss.elastic.co/u/Jagmee)\ **Post date:** [February 28, 2011, 8:35pm UTC](https://discuss.elastic.co/t/restarting-es-service-frequently-for-memory-issue/3997/1 "2011-02-28T20:35:44Z")
Hi, Some times I have noticed below warning MSG in ES Data Node [02:45:15,291][WARN][transport.netty] [Lin Sun] Exception caught on n etty layer [[id: 0x339db231, /10.2.216.60:1705 =\> /10.2.216.10:9300]] java.io.IOException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full at sun.nio.ch.SocketDispatcher.write0(Native Method) at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:33) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:100) at sun.nio.ch.IOUtil.write(IOUtil.java:71) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java: 334) at org.elasticsearch.common.netty.channel.socket.nio.SocketSendBufferPoo l$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:202) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.write0(Ni oWorker.java:470) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.writeFrom TaskLoop(NioWorker.java:393) at org.elasticsearch.common.netty.channel.socket.nio.NioSocketChannel$Wr iteTask.run(NioSocketChannel.java:268) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processWr iteTaskQueue(NioWorker.java:269) at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWo rker.java:200) at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(Thread RenamingRunnable.java:108) at org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoW orkerRunnable.java:46) at java.util.concurrent.ThreadPoolExecutor $Worker.runTask(ThreadPoolExec utor.java:886) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor .java:908) at java.lang.Thread.run(Thread.java:619) [03:17:17,152][INFO][monitor.jvm] [Lin Sun] [gc] [ConcurrentMarkSw eep][2] took [15.1m]/[15.1m], reclaimed [4.1gb], leaving [3.8gb] used, max [8.1g b] [03:36:42,138][INFO][monitor.jvm] [Lin Sun] [gc][ParNew] [20145] t ook [44s]/[13m], reclaimed [122.9mb], leaving [3.8gb] used, max [8.1gb] [04:11:59,017][INFO][monitor.jvm] [Lin Sun] [gc][ParNew] [20146] t ook [42.4s]/[13.7m], reclaimed [135.7mb], leaving [3.8gb] used, max [8.1gb] At this time some Database(large Size DB) was not working properly and getting slowly, after restart it's come normal. 1. Is this a memory problem if we increase the memory size will this issue will get solved ? Or we have to do some maintenance work regularly? 2. How to we fix this without restarting ES? Note: Configured MAX memory size is 8 GB Thanks, -Jagmee ---
**Author:** ![Karussell1](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@Karussell1](https://discuss.elastic.co/u/Karussell1)\ **Post date:** [March 1, 2011, 8:01pm UTC](https://discuss.elastic.co/t/restarting-es-service-frequently-for-memory-issue/3997/2 "2011-03-01T20:01:39Z")
are you running 0.15 where a lot memory enhancements were made? Regards, Peter -- [http://jetwick.com](http://jetwick.com) Personalized Twitter Search On 28 Feb., 21:35, Jagmee [jagmee...@gmail.com](mailto:jagmee...@gmail.com) wrote: > Hi, > > Some times I have noticed below warning MSG in ES Data Node > > [02:45:15,291][WARN][transport.netty] [Lin Sun] Exception > caught on n > etty layer [[id: 0x339db231, /10.2.216.60:1705 =\> /10.2.216.10:9300]] > java.io.IOException: An operation on a socket could not be performed > because the > system lacked sufficient buffer space or because a queue was full > at sun.nio.ch.SocketDispatcher.write0(Native Method) > at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:33) > at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:100) > at sun.nio.ch.IOUtil.write(IOUtil.java:71) > at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java: > 334) > at > org.elasticsearch.common.netty.channel.socket.nio.SocketSendBufferPoo > l$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:202) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.write0(Ni > oWorker.java:470) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.writeFrom > TaskLoop(NioWorker.java:393) > at > org.elasticsearch.common.netty.channel.socket.nio.NioSocketChannel$Wr > iteTask.run(NioSocketChannel.java:268) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processWr > iteTaskQueue(NioWorker.java:269) > at > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWo > rker.java:200) > at > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(Thread > RenamingRunnable.java:108) > at > org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoW > orkerRunnable.java:46) > at java.util.concurrent.ThreadPoolExecutor > $Worker.runTask(ThreadPoolExec > utor.java:886) > at java.util.concurrent.ThreadPoolExecutor > $Worker.run(ThreadPoolExecutor > .java:908) > at java.lang.Thread.run(Thread.java:619) > [03:17:17,152][INFO][monitor.jvm] [Lin Sun] [gc] > [ConcurrentMarkSw > eep][2] took [15.1m]/[15.1m], reclaimed [4.1gb], leaving [3.8gb] used, > max [8.1g > b] > [03:36:42,138][INFO][monitor.jvm] [Lin Sun] [gc][ParNew] > [20145] t > ook [44s]/[13m], reclaimed [122.9mb], leaving [3.8gb] used, max > [8.1gb] > [04:11:59,017][INFO][monitor.jvm] [Lin Sun] [gc][ParNew] > [20146] t > ook [42.4s]/[13.7m], reclaimed [135.7mb], leaving [3.8gb] used, max > [8.1gb] > > At this time some Database(large Size DB) was not working properly and > getting slowly, after restart it's come normal. > > 1. Is this a memory problem if we increase the memory size will this > issue will get solved ? Or we have to do some maintenance work > regularly? > 2. How to we fix this without restarting ES? > > Note: Configured MAX memory size is 8 GB > > Thanks, > -Jagmee ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [March 2, 2011, 12:36am UTC](https://discuss.elastic.co/t/restarting-es-service-frequently-for-memory-issue/3997/3 "2011-03-02T00:36:31Z")
If you are running windows, check this first google hit: [http://blogs.msdn.com/b/sql\_protocols/archive/2009/03/09/understanding-the-error-an-operation-on-a-socket-could-not-be-performed-because-the-system-lacked-sufficient-buffer-space-or-because-a-queue-was-full.aspx](http://blogs.msdn.com/b/sql_protocols/archive/2009/03/09/understanding-the-error-an-operation-on-a-socket-could-not-be-performed-because-the-system-lacked-sufficient-buffer-space-or-because-a-queue-was-full.aspx) for the error message. On Tuesday, March 1, 2011 at 10:01 PM, Karussell wrote: > are you running 0.15 where a lot memory enhancements were made? > > Regards, > Peter > > -- > > [http://jetwick.com](http://jetwick.com) Personalized Twitter Search > > On 28 Feb., 21:35, Jagmee [jagmee...@gmail.com](mailto:jagmee...@gmail.com) wrote: > > > Hi, > > > > Some times I have noticed below warning MSG in ES Data Node > > > > [02:45:15,291][WARN][transport.netty] [Lin Sun] Exception > > caught on n > > etty layer [[id: 0x339db231, /10.2.216.60:1705 =\> /10.2.216.10:9300]] > > java.io.IOException: An operation on a socket could not be performed > > because the > > system lacked sufficient buffer space or because a queue was full > > at sun.nio.ch.SocketDispatcher.write0(Native Method) > > at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:33) > > at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:100) > > at sun.nio.ch.IOUtil.write(IOUtil.java:71) > > at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java: > > 334) > > at > > org.elasticsearch.common.netty.channel.socket.nio.SocketSendBufferPoo > > l$UnpooledSendBuffer.transferTo(SocketSendBufferPool.java:202) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.write0(Ni > > oWorker.java:470) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.writeFrom > > TaskLoop(NioWorker.java:393) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioSocketChannel$Wr > > iteTask.run(NioSocketChannel.java:268) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.processWr > > iteTaskQueue(NioWorker.java:269) > > at > > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWo > > rker.java:200) > > at > > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(Thread > > RenamingRunnable.java:108) > > at > > org.elasticsearch.common.netty.util.internal.IoWorkerRunnable.run(IoW > > orkerRunnable.java:46) > > at java.util.concurrent.ThreadPoolExecutor > > $Worker.runTask(ThreadPoolExec > > utor.java:886) > > at java.util.concurrent.ThreadPoolExecutor > > $Worker.run(ThreadPoolExecutor > > .java:908) > > at java.lang.Thread.run(Thread.java:619) > > [03:17:17,152][INFO][monitor.jvm] [Lin Sun] [gc] > > [ConcurrentMarkSw > > eep][2] took [15.1m]/[15.1m], reclaimed [4.1gb], leaving [3.8gb] used, > > max [8.1g > > b] > > [03:36:42,138][INFO][monitor.jvm] [Lin Sun] [gc][ParNew] > > [20145] t > > ook [44s]/[13m], reclaimed [122.9mb], leaving [3.8gb] used, max > > [8.1gb] > > [04:11:59,017][INFO][monitor.jvm] [Lin Sun] [gc][ParNew] > > [20146] t > > ook [42.4s]/[13.7m], reclaimed [135.7mb], leaving [3.8gb] used, max > > [8.1gb] > > > > At this time some Database(large Size DB) was not working properly and > > getting slowly, after restart it's come normal. > > > > 1. Is this a memory problem if we increase the memory size will this > > issue will get solved ? Or we have to do some maintenance work > > regularly? > > 2. How to we fix this without restarting ES? > > > > Note: Configured MAX memory size is 8 GB > > > > Thanks, > > -Jagmee ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 4:11am UTC](https://discuss.elastic.co/t/restarting-es-service-frequently-for-memory-issue/3997/4 "2017-07-06T04:11:08Z")
Closed on July 6, 2017, 4:11am UTC