# Is this a bug？

**URL:** <https://discuss.elastic.co/t/is-this-a-bug/7990>\
**Category:** Elasticsearch\
**Created:** [June 6, 2012, 4:49am UTC](https://discuss.elastic.co/t/is-this-a-bug/7990 "2012-06-06T04:49:51Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![zhouxiang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhouxiang/32/2775_2.png) [@zhouxiang](https://discuss.elastic.co/u/zhouxiang)\
**Post date:** [June 6, 2012, 4:49am UTC](https://discuss.elastic.co/t/is-this-a-bug/7990/1 "2012-06-06T04:49:51Z")

</div>

yesterday the es didn't serve the query request.every request is time out.after restart the cluster it recovered.every request took much time to excute.And,the request num become too large,then the cpu usage very high.  
log is :  
[2012-06-05 19:50:12,867][DEBUG][http.netty] [Brynocki] Caught exception while handling client http traffic, closing connection [id: 0x48c71e8c, /10.61.4.1:33808 =\> /10.61.14  
.1:9200]  
java.io.IOException: Connection reset by peer  
at sun.nio.ch.SocketDispatcher.read0(Native Method)  
at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:20)  
at sun.nio.ch.IOUtil.read(IOUtil.java:247)  
at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)  
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:66)  
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:372)  
at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:246)  
at org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:38)  
at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102)  
at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)  
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)  
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)  
at java.lang.Thread.run(Thread.java:662)

---

<div class="post-metadata">

**Author:** ![zhouxiang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhouxiang/32/2775_2.png) [@zhouxiang](https://discuss.elastic.co/u/zhouxiang)\
**Post date:** [June 6, 2012, 6:54am UTC](https://discuss.elastic.co/t/is-this-a-bug/7990/2 "2012-06-06T06:54:10Z")

</div>

i guess es excute much time to complete a request.bebore it the client  
close the connection then retry.  
the current request number is too large,then out of resource.

but the requests are all the same pattern,after restart it,it is ok.

在 2012年6月6日星期三UTC+8下午12时49分51秒，shinezhou写道：

> yesterday the es didn't serve the query request.every request is time  
> out.after restart the cluster it recovered.every request took much time to  
> excute.And,the request num become too large,then the cpu usage very high.  
> log is :  
> [2012-06-05 19:50:12,867][DEBUG][http.netty] [Brynocki]  
> Caught exception while handling client http traffic, closing connection  
> [id:  
> 0x48c71e8c, /10.61.4.1:33808 =\> /10.61.14  
> .1:9200]  
> java.io.IOException: Connection reset by peer  
> at sun.nio.ch.SocketDispatcher.read0(Native Method)  
> at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:20)  
> at sun.nio.ch.IOUtil.read(IOUtil.java:247)  
> at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)  
> at  
> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:66)
> 
> ```
> at 
> 
> ```
> 
> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:372)
> 
> ```
> at 
> 
> ```
> 
> org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:246)
> 
> ```
> at 
> 
> ```
> 
> org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:38)
> 
> ```
> at 
> 
> ```
> 
> org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102)
> 
> ```
> at 
> 
> ```
> 
> org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
> 
> ```
> at 
> 
> ```
> 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> 
> ```
> at 
> 
> ```
> 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> 
> ```
> at java.lang.Thread.run(Thread.java:662) 
> 
> ```
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/is-this-a-bug-tp4018865.html](http://elasticsearch-users.115913.n3.nabble.com/is-this-a-bug-tp4018865.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![zhouxiang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhouxiang/32/2775_2.png) [@zhouxiang](https://discuss.elastic.co/u/zhouxiang)\
**Post date:** [June 6, 2012, 7:16am UTC](https://discuss.elastic.co/t/is-this-a-bug/7990/3 "2012-06-06T07:16:02Z")

</div>

during that time ，the whole cluster can not serve the query request。but can  
serve the index request。so confuse。

在 2012年6月6日星期三UTC+8下午2时54分10秒，shinezhou写道：

> i guess es excute much time to complete a request.bebore it the client  
> close the connection then retry.  
> the current request number is too large,then out of resource.
> 
> but the requests are all the same pattern,after restart it,it is ok.
> 
> 在 2012年6月6日星期三UTC+8下午12时49分51秒，shinezhou写道：
> 
> > yesterday the es didn't serve the query request.every request is time  
> > out.after restart the cluster it recovered.every request took much time  
> > to  
> > excute.And,the request num become too large,then the cpu usage very high.  
> > log is :  
> > [2012-06-05 19:50:12,867][DEBUG][http.netty] [Brynocki]  
> > Caught exception while handling client http traffic, closing connection  
> > [id:  
> > 0x48c71e8c, /10.61.4.1:33808 =\> /10.61.14  
> > .1:9200]  
> > java.io.IOException: Connection reset by peer  
> > at sun.nio.ch.SocketDispatcher.read0(Native Method)  
> > at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:20)  
> > at sun.nio.ch.IOUtil.read(IOUtil.java:247)  
> > at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:243)  
> > at  
> > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.read(NioWorker.java:66)
> > 
> > ```
> > at 
> > 
> > ```
> > 
> > org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.processSelectedKeys(AbstractNioWorker.java:372)
> > 
> > ```
> > at 
> > 
> > ```
> > 
> > org.elasticsearch.common.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:246)
> > 
> > ```
> > at 
> > 
> > ```
> > 
> > org.elasticsearch.common.netty.channel.socket.nio.NioWorker.run(NioWorker.java:38)
> > 
> > ```
> > at 
> > 
> > ```
> > 
> > org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:102)
> > 
> > ```
> > at 
> > 
> > ```
> > 
> > org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)
> > 
> > ```
> > at 
> > 
> > ```
> > 
> > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> > 
> > ```
> > at 
> > 
> > ```
> > 
> > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> > 
> > ```
> > at java.lang.Thread.run(Thread.java:662) 
> > 
> > ```
> > 
> > --  
> > View this message in context:  
> > [http://elasticsearch-users.115913.n3.nabble.com/is-this-a-bug-tp4018865.html](http://elasticsearch-users.115913.n3.nabble.com/is-this-a-bug-tp4018865.html)  
> > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**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:** [June 10, 2012, 9:18pm UTC](https://discuss.elastic.co/t/is-this-a-bug/7990/4 "2012-06-10T21:18:54Z")

</div>

Can you share the search request you executed?

On Wed, Jun 6, 2012 at 9:16 AM, shinezhou [zhouxiang@baixing.com](mailto:zhouxiang@baixing.com) wrote:

> during that time ，the whole cluster can not serve the query request。but  
> can serve the index request。so confuse。
> 
> 在 2012年6月6日星期三UTC+8下午2时54分10秒，shinezhou写道：
> 
> > i guess es excute much time to complete a request.bebore it the client  
> > close the connection then retry.  
> > the current request number is too large,then out of resource.
> > 
> > but the requests are all the same pattern,after restart it,it is ok.
> > 
> > 在 2012年6月6日星期三UTC+8下午12时49分51秒，\*\*shinezhou写道：
> > 
> > > yesterday the es didn't serve the query request.every request is time  
> > > out.after restart the cluster it recovered.every request took much time  
> > > to  
> > > excute.And,the request num become too large,then the cpu usage very  
> > > high.  
> > > log is :  
> > > [2012-06-05 19:50:12,867][DEBUG][http.\*\*netty]  
> > > [Brynocki]  
> > > Caught exception while handling client http traffic, closing connection  
> > > [id:  
> > > 0x48c71e8c, /10.61.4.1:33808 =\> /10.61.14  
> > > .1:9200]  
> > > java.io.IOException: Connection reset by peer  
> > > at sun.nio.ch.SocketDispatcher.\*\*read0(Native Method)  
> > > at sun.nio.ch.SocketDispatcher.\*\*read(SocketDispatcher.java:20)  
> > > at sun.nio.ch.IOUtil.read(IOUtil.\*\*java:247)  
> > > at sun.nio.ch.SocketChannelImpl.\*\*read(SocketChannelImpl.java:\*\*243)
> > > 
> > > ```
> > > at
> > > 
> > > ```
> > > 
> > > org.elasticsearch.common. **netty.channel.socket.nio.**  
> > > NioWorker.read(NioWorker.java:\*\*66)  
> > > at  
> > > org.elasticsearch.common.\*\*netty.channel.socket.nio.\*\*AbstractNioWorker.  
> > > \*\*processSelectedKeys(\*\*AbstractNioWorker.java:372)  
> > > at  
> > > org.elasticsearch.common. **netty.channel.socket.nio.**  
> > > AbstractNioWorker.run(\*\*AbstractNioWorker.java:246)  
> > > at  
> > > org.elasticsearch.common. **netty.channel.socket.nio.**  
> > > NioWorker.run(NioWorker.java:\*\*38)  
> > > at  
> > > org.elasticsearch.common.\*\*netty.util.**ThreadRenamingRunnable.run(**  
> > > ThreadRenamingRunnable.java:\*\*102)  
> > > at  
> > > org.elasticsearch.common. **netty.util.internal.**  
> > > DeadLockProofWorker$1.run(\*\*DeadLockProofWorker.java:42)  
> > > at  
> > > java.util.concurrent. **ThreadPoolExecutor$Worker.**  
> > > runTask(ThreadPoolExecutor.\*\*java:886)  
> > > at  
> > > java.util.concurrent.\*\*ThreadPoolExecutor$Worker.run(\*\*ThreadPoolExecutor.java:908)
> > > 
> > > ```
> > > at java.lang.Thread.run(Thread.**java:662)
> > > 
> > > ```
> > > 
> > > --  
> > > View this message in context: [http://elasticsearch-users](http://elasticsearch-users).\*\*  
> > > [115913.n3.nabble.com/is-this-\*\*a-bug-tp4018865.html](http://115913.n3.nabble.com/is-this-**a-bug-tp4018865.html)[http://elasticsearch-users.115913.n3.nabble.com/is-this-a-bug-tp4018865.html](http://elasticsearch-users.115913.n3.nabble.com/is-this-a-bug-tp4018865.html)  
> > > Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

---

<div class="post-metadata">

**Author:** ![zhouxiang](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zhouxiang/32/2775_2.png) [@zhouxiang](https://discuss.elastic.co/u/zhouxiang)\
**Post date:** [June 13, 2012, 3:00am UTC](https://discuss.elastic.co/t/is-this-a-bug/7990/5 "2012-06-13T03:00:22Z")

</div>

query all just like this  
{"query":{"bool":{"must":[{"term":{"idType":"mobile"}},{"term":{"idValue":"18601772452"}},{"term":{"status":"1"}},{"terms":{"bangui":["违法违规","虚假欺诈","临时禁发","电话号码盗用"],"minimum\_match":1}},{"range":{"createdTime":{"from":"20120214T105915Z","to":"20120613T105915Z"}}}]}},"fields":["id"],"sort":{"id":{"order":"asc"}},"size":2000}

these days the es is very well.

---

<div class="post-metadata">

**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, 3:24am UTC](https://discuss.elastic.co/t/is-this-a-bug/7990/6 "2017-07-06T03:24:42Z")

</div>