# Major Bug in 0.17.x and 0.18.x (up to 0.18.2)

**URL:** <https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874>\
**Category:** Elasticsearch\
**Created:** [November 15, 2011, 6:56am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874 "2011-11-15T06:56:41Z")\
**Posts on this page:** 18\
**Page:** 1

<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:** [November 15, 2011, 6:56am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/1 "2011-11-15T06:56:41Z")

</div>

Hey,

```
I posted before as a reply to a thread, but it should be on its own

```

thread and notice. A major bug was found in 0.17.x versions and 0.18.x (up  
to and including 0.18.2):  
[https://github.com/elasticsearch/elasticsearch/issues/1455](https://github.com/elasticsearch/elasticsearch/issues/1455). This bug means  
that under load, with long running search requests, the node can become  
unresponsive and not handle requests properly.

There is already a fix in master and 0.18 branch, and 0.18.3 will be  
released either today or tomorrow. Wanted to get feedback if a 0.17.10 with  
the fix should be released as well. I prefer users who upgrade to upgrade  
to 0.18 while they are at it, but understand if there is a need for 0.17  
release.

-shay.banon

---

<div class="post-metadata">

**Author:** ![Patrick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/patrick/32/1437_2.png) [@Patrick](https://discuss.elastic.co/u/Patrick)\
**Post date:** [November 15, 2011, 7:01am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/2 "2011-11-15T07:01:34Z")

</div>

I had some reports from a few friends that when they tried to bump  
their installations of 0.17 to 0.18 (for daikon), logstash didn't play  
well with it. I'm not sure how much of a factor that would play, but  
I'd assume that quite a few of those unfortunate souls would love the  
upgrade, but worry about the breakage.

## Patrick

> **[Patrick Ancillotti on about.me](https://about.me/patrick.ancillotti)**
>
> I live in New York.

patrick eefy net

On Tue, Nov 15, 2011 at 12:56 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:

> Hey,  
> I posted before as a reply to a thread, but it should be on its own  
> thread and notice. A major bug was found in 0.17.x versions and 0.18.x (up  
> to and including  
> 0.18.2): [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455). This  
> bug means that under load, with long running search requests, the node can  
> become unresponsive and not handle requests properly.  
> There is already a fix in master and 0.18 branch, and 0.18.3 will be  
> released either today or tomorrow. Wanted to get feedback if a 0.17.10 with  
> the fix should be released as well. I prefer users who upgrade to upgrade to  
> 0.18 while they are at it, but understand if there is a need for 0.17  
> release.  
> -shay.banon

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 15, 2011, 7:06am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/3 "2011-11-15T07:06:19Z")

</div>

At first, I would use 0.17 in production in the next weeks but I will switch to 0.18 as you suggest.

So at the present time, I don't need a new release of 0.17.

Thanks  
David 😉  
@dadoonet

Le 15 nov. 2011 à 07:56, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit :

> Hey,
> 
> ```
> I posted before as a reply to a thread, but it should be on its own thread and notice. A major bug was found in 0.17.x versions and 0.18.x (up to and including 0.18.2): https://github.com/elasticsearch/elasticsearch/issues/1455. This bug means that under load, with long running search requests, the node can become unresponsive and not handle requests properly.
> 
> ```
> 
> There is already a fix in master and 0.18 branch, and 0.18.3 will be released either today or tomorrow. Wanted to get feedback if a 0.17.10 with the fix should be released as well. I prefer users who upgrade to upgrade to 0.18 while they are at it, but understand if there is a need for 0.17 release.
> 
> -shay.banon

---

<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:** [November 15, 2011, 7:42am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/4 "2011-11-15T07:42:30Z")

</div>

I applied the fix to the 0.17 branch in any case, btw.

On Tue, Nov 15, 2011 at 9:06 AM, David Pilato [david@pilato.fr](mailto:david@pilato.fr) wrote:

> At first, I would use 0.17 in production in the next weeks but I will  
> switch to 0.18 as you suggest.
> 
> So at the present time, I don't need a new release of 0.17.
> 
> Thanks  
> David 😉  
> @dadoonet
> 
> Le 15 nov. 2011 à 07:56, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) a écrit :
> 
> Hey,
> 
> ```
> I posted before as a reply to a thread, but it should be on its own
> 
> ```
> 
> thread and notice. A major bug was found in 0.17.x versions and 0.18.x (up  
> to and including 0.18.2): [https://github.com/elasticsearch/elasticsearch/issues/1455](https://github.com/elasticsearch/elasticsearch/issues/1455)  
> [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455). This bug  
> means that under load, with long running search requests, the node can  
> become unresponsive and not handle requests properly.
> 
> There is already a fix in master and 0.18 branch, and 0.18.3 will be  
> released either today or tomorrow. Wanted to get feedback if a 0.17.10 with  
> the fix should be released as well. I prefer users who upgrade to upgrade  
> to 0.18 while they are at it, but understand if there is a need for 0.17  
> release.
> 
> -shay.banon

---

<div class="post-metadata">

**Author:** ![Lukas\_Vlcek1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukas_vlcek1/32/819_2.png) [@Lukas\_Vlcek1](https://discuss.elastic.co/u/Lukas_Vlcek1)\
**Post date:** [November 15, 2011, 8:18am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/5 "2011-11-15T08:18:47Z")

</div>

Hi,

what is the chance of hitting this issue when requests are executed with a  
timeout option with 0.18.2 ?

Regards,  
Lukáš  
Dne 15.11.2011 7:57 "Shay Banon" [kimchy@gmail.com](mailto:kimchy@gmail.com) napsal(a):

> Hey,
> 
> ```
> I posted before as a reply to a thread, but it should be on its own
> 
> ```
> 
> thread and notice. A major bug was found in 0.17.x versions and 0.18.x (up  
> to and including 0.18.2):  
> [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455). This bug  
> means that under load, with long running search requests, the node can  
> become unresponsive and not handle requests properly.
> 
> There is already a fix in master and 0.18 branch, and 0.18.3 will be  
> released either today or tomorrow. Wanted to get feedback if a 0.17.10 with  
> the fix should be released as well. I prefer users who upgrade to upgrade  
> to 0.18 while they are at it, but understand if there is a need for 0.17  
> release.
> 
> -shay.banon

---

<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:** [November 15, 2011, 9:14am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/6 "2011-11-15T09:14:44Z")

</div>

Similar, though timeout will bound the execution (though its not perfect).

On Tue, Nov 15, 2011 at 10:18 AM, Lukáš Vlček [lukas.vlcek@gmail.com](mailto:lukas.vlcek@gmail.com) wrote:

> Hi,
> 
> what is the chance of hitting this issue when requests are executed with a  
> timeout option with 0.18.2 ?
> 
> Regards,  
> Lukáš  
> Dne 15.11.2011 7:57 "Shay Banon" [kimchy@gmail.com](mailto:kimchy@gmail.com) napsal(a):
> 
> Hey,
> 
> > ```
> > I posted before as a reply to a thread, but it should be on its own
> > 
> > ```
> > 
> > thread and notice. A major bug was found in 0.17.x versions and 0.18.x (up  
> > to and including 0.18.2):  
> > [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455). This bug  
> > means that under load, with long running search requests, the node can  
> > become unresponsive and not handle requests properly.
> > 
> > There is already a fix in master and 0.18 branch, and 0.18.3 will be  
> > released either today or tomorrow. Wanted to get feedback if a 0.17.10 with  
> > the fix should be released as well. I prefer users who upgrade to upgrade  
> > to 0.18 while they are at it, but understand if there is a need for 0.17  
> > release.
> > 
> > -shay.banon

---

<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:** [November 15, 2011, 9:15am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/7 "2011-11-15T09:15:40Z")

</div>

Can they provide more details? Maybe its because logstash embeds  
elasticsearch, and upgrading the "server" side of elasticsearch to 0.18  
also requires upgrading the embedded version in logstash as well.

On Tue, Nov 15, 2011 at 9:01 AM, Patrick [patrick@eefy.net](mailto:patrick@eefy.net) wrote:

> I had some reports from a few friends that when they tried to bump  
> their installations of 0.17 to 0.18 (for daikon), logstash didn't play  
> well with it. I'm not sure how much of a factor that would play, but  
> I'd assume that quite a few of those unfortunate souls would love the  
> upgrade, but worry about the breakage.
> 
> ## Patrick
> 
> [Patrick Ancillotti - New York | about.me](http://about.me/patrick.ancillotti)  
> patrick eefy net
> 
> On Tue, Nov 15, 2011 at 12:56 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> 
> > Hey,  
> > I posted before as a reply to a thread, but it should be on its own  
> > thread and notice. A major bug was found in 0.17.x versions and 0.18.x  
> > (up  
> > to and including  
> > 0.18.2): [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455).  
> > This  
> > bug means that under load, with long running search requests, the node  
> > can  
> > become unresponsive and not handle requests properly.  
> > There is already a fix in master and 0.18 branch, and 0.18.3 will be  
> > released either today or tomorrow. Wanted to get feedback if a 0.17.10  
> > with  
> > the fix should be released as well. I prefer users who upgrade to  
> > upgrade to  
> > 0.18 while they are at it, but understand if there is a need for 0.17  
> > release.  
> > -shay.banon

---

<div class="post-metadata">

**Author:** ![medcl\_net](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@medcl\_net](https://discuss.elastic.co/u/medcl_net)\
**Post date:** [November 15, 2011, 10:19am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/8 "2011-11-15T10:19:05Z")

</div>

Hi,

```
I just found an interesting issue，when setting filter‘s cache to be true, different position of the parameter “size” will introduce different result size.

```

1.set cache to true,and the “from” “size” are after “query”.

{"query":{"constant\_score":{"filter":{"query":{term: { "gender" : { "term" : "true", "boost":1 }} },"\_cache": true},"boost": 1}},"from": 0,"size": 6,"explain": false}

it return 10 hits ,so there is not correct.

2.and now remove the cache parameter  
{"query":{"constant\_score":{"filter":{"query":{term: { "gender" : { "term" : "true", "boost":1 }} }},"boost": 1}},"from": 0,"size": 6,"explain": false}

what I got is 6 hits,k,it’s right.

3.now back to the first query,and do little change,I moved the “from” “size” in front of “query”  
{"from": 0,"size": 6,"query":{"constant\_score":{"filter":{"query":{term: { "gender" : { "term" : "true", "boost":1 }} },"\_cache": true},"boost": 1}},"explain": false}

and now what I got is 6 hits.

I think this issue matters,so reported there. .  
BTW,and a parameter to the url,such as“[http://host:9200/index/type/\_search?size=6”](http://host:9200/index/type/_search?size=6%E2%80%9D) does works.

these tests and under clean environment.

yours sincerely,  
medcl  
[http://log.medcl.net](http://log.medcl.net)

---

<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:** [November 15, 2011, 10:58am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/9 "2011-11-15T10:58:48Z")

</div>

Its because the placement of the \_cache element is incorrect, it should on  
the same level as filter, not within it. I still need to check why it does  
not fail properly in this case.

Btw, why such complex query? Seems like what you need is just a term filter  
within the constant\_score, why wrap it in a query filter that wraps a term  
query?

On Tue, Nov 15, 2011 at 12:19 PM, [medcl2000@gmail.com](mailto:medcl2000@gmail.com) wrote:

> Hi,
> 
> ```
> I just found an interesting issue，when setting filter‘s cache to be
> 
> ```
> 
> true, different position of the parameter “size” will introduce different  
> result size.
> 
> 1.set cache to true,and the “from” “size” are after “query”.
> 
> {"query":{"constant\_score":{"filter":{"query":{term: { "gender" : { "term"  
> : "true", "boost":1 }} },"\_cache": true},"boost": 1}},"from": 0\*,"size": 6  
> \*,"explain": false}
> 
> it return 10 hits ,so there is not correct.
> 
> 2.and now remove the cache parameter  
> {"query":{"constant\_score":{"filter":{"query":{term: { "gender" : { "term"  
> : "true", "boost":1 }} }},"boost": 1}},"from": 0,"size": 6,"explain":  
> false}
> 
> what I got is 6 hits,k,it’s right.
> 
> 3.now back to the first query,and do little change,I moved the “from”  
> “size” in front of “query”  
> {"from": 0\*,"size": 6\*,"query":{"constant\_score":{"filter":{"query":{term:  
> { "gender" : { "term" : "true", "boost":1 }} },"\_cache": true},"boost":  
> 1}},"explain": false}
> 
> and now what I got is 6 hits.
> 
> I think this issue matters,so reported there. [image: Smile].  
> BTW,and a parameter to the url,such as“  
> [http://host:9200/index/type/\_search?size=6”](http://host:9200/index/type/_search?size=6%E2%80%9D) does works.
> 
> these tests and under clean environment.
> 
> yours sincerely,  
> medcl  
> [http://log.medcl.net](http://log.medcl.net)

---

<div class="post-metadata">

**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\
**Post date:** [November 15, 2011, 11:00am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/10 "2011-11-15T11:00:49Z")

</div>

Hi medcl

> 1.set cache to true,and the “from” “size” are after “query”.
> 
> {"query":{"constant\_score":{"filter":{"query":{term: { "gender" :  
> { "term" : "true", "boost":1 }} },"\_cache": true},"boost": 1}},"from":  
> 0,"size": 6,"explain": false}

With a cached query filter, you need to wrap the "query" and "\_cache"  
parameters in an 'fquery' element:

```
"filter" : {
    fquery : {
        "query" : {
            term : {
                "gender" : { "term" : "true", "boost" : 1 }
            }
        },
        "_cache" : true
    }
},

```

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

That said, why are you using a query filter at all?

Your query would be better written as:

{  
"query" : {  
"constant\_score" : {  
"filter" : {  
"term" : {  
"gender" : "true"  
}  
}  
}  
}  
}

And that filter would be cached by default.

clint

---

<div class="post-metadata">

**Author:** ![medcl\_net](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@medcl\_net](https://discuss.elastic.co/u/medcl_net)\
**Post date:** [November 15, 2011, 2:24pm UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/11 "2011-11-15T14:24:11Z")

</div>

hi,  
thanks for you quickly reply,I just tried to wrapper a queryDSL layer  
,my bad,and seems lots of work need to do.

-----Original Message-----  
From: Clinton Gormley  
Sent: Tuesday, November 15, 2011 7:00 PM  
To: [elasticsearch@googlegroups.com](mailto:elasticsearch@googlegroups.com)  
Subject: Re: issue about size when set filter cached

Hi medcl

> 1.set cache to true,and the “from” “size” are after “query”.
> 
> {"query":{"constant\_score":{"filter":{"query":{term: { "gender" :  
> { "term" : "true", "boost":1 }} },"\_cache": true},"boost": 1}},"from":  
> 0,"size": 6,"explain": false}

With a cached query filter, you need to wrap the "query" and "\_cache"  
parameters in an 'fquery' element:

```
"filter" : {
    fquery : {
        "query" : {
            term : {
                "gender" : { "term" : "true", "boost" : 1 }
            }
        },
        "_cache" : true
    }
},

```

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

That said, why are you using a query filter at all?

Your query would be better written as:

{  
"query" : {  
"constant\_score" : {  
"filter" : {  
"term" : {  
"gender" : "true"  
}  
}  
}  
}  
}

And that filter would be cached by default.

clint

---

<div class="post-metadata">

**Author:** ![Frederic](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@Frederic](https://discuss.elastic.co/u/Frederic)\
**Post date:** [November 15, 2011, 3:02pm UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/12 "2011-11-15T15:02:37Z")

</div>

Hi Shay,

Thanks for the update and fix. We would certainly need the 0.17.x fix  
for our systems in production, while I test the upgrade to 0.18 in the  
meantime.

Simple question though: in these case, is it equally required to  
update clients as well? we have both Transport and Node clients  
connected to our ES cluster.

Thanks,

On 15 nov, 04:42, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:

> I applied the fix to the 0.17 branch in any case, btw.
> 
> On Tue, Nov 15, 2011 at 9:06 AM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote:
> 
> > At first, I would use 0.17 in production in the next weeks but I will  
> > switch to 0.18 as you suggest.
> 
> > So at the present time, I don't need a new release of 0.17.
> 
> > Thanks  
> > David 😉  
> > @dadoonet
> 
> > Le 15 nov. 2011 à 07:56, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) a écrit :
> 
> > Hey,
> 
> > ```
> > I posted before as a reply to a thread, but it should be on its own
> > 
> > ```
> > 
> > thread and notice. A major bug was found in 0.17.x versions and 0.18.x (up  
> > to and including 0.18.2): [https://github.com/elasticsearch/elasticsearch/issues/1455](https://github.com/elasticsearch/elasticsearch/issues/1455)  
> > [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455). This bug  
> > means that under load, with long running search requests, the node can  
> > become unresponsive and not handle requests properly.
> 
> > There is already a fix in master and 0.18 branch, and 0.18.3 will be  
> > released either today or tomorrow. Wanted to get feedback if a 0.17.10 with  
> > the fix should be released as well. I prefer users who upgrade to upgrade  
> > to 0.18 while they are at it, but understand if there is a need for 0.17  
> > release.
> 
> > -shay.banon

---

<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:** [November 15, 2011, 4:13pm UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/13 "2011-11-15T16:13:25Z")

</div>

One user is enough :), I will release 0.17.10 either tonight or tomorrow.

On Tue, Nov 15, 2011 at 5:02 PM, Frederic [focampo.br@gmail.com](mailto:focampo.br@gmail.com) wrote:

> Hi Shay,
> 
> Thanks for the update and fix. We would certainly need the 0.17.x fix  
> for our systems in production, while I test the upgrade to 0.18 in the  
> meantime.
> 
> Simple question though: in these case, is it equally required to  
> update clients as well? we have both Transport and Node clients  
> connected to our ES cluster.
> 
> Thanks,
> 
> On 15 nov, 04:42, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> 
> > I applied the fix to the 0.17 branch in any case, btw.
> > 
> > On Tue, Nov 15, 2011 at 9:06 AM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote:
> > 
> > > At first, I would use 0.17 in production in the next weeks but I will  
> > > switch to 0.18 as you suggest.
> > 
> > > So at the present time, I don't need a new release of 0.17.
> > 
> > > Thanks  
> > > David 😉  
> > > @dadoonet
> > 
> > > Le 15 nov. 2011 à 07:56, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) a écrit :
> > 
> > > Hey,
> > 
> > > ```
> > > I posted before as a reply to a thread, but it should be on its own
> > > 
> > > ```
> > > 
> > > thread and notice. A major bug was found in 0.17.x versions and 0.18.x  
> > > (up  
> > > to and including 0.18.2): \<  
> > > [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455)\>  
> > > [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455). This bug  
> > > means that under load, with long running search requests, the node can  
> > > become unresponsive and not handle requests properly.
> > 
> > > There is already a fix in master and 0.18 branch, and 0.18.3 will be  
> > > released either today or tomorrow. Wanted to get feedback if a 0.17.10  
> > > with  
> > > the fix should be released as well. I prefer users who upgrade to  
> > > upgrade  
> > > to 0.18 while they are at it, but understand if there is a need for  
> > > 0.17  
> > > release.
> > 
> > > -shay.banon

---

<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:** [November 16, 2011, 10:54am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/14 "2011-11-16T10:54:24Z")

</div>

0.17.10 has just been released. I want to fix another bug in 0.18 and then  
release 0.18.3 today.

On Tue, Nov 15, 2011 at 6:13 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:

> One user is enough :), I will release 0.17.10 either tonight or tomorrow.
> 
> On Tue, Nov 15, 2011 at 5:02 PM, Frederic [focampo.br@gmail.com](mailto:focampo.br@gmail.com) wrote:
> 
> > Hi Shay,
> > 
> > Thanks for the update and fix. We would certainly need the 0.17.x fix  
> > for our systems in production, while I test the upgrade to 0.18 in the  
> > meantime.
> > 
> > Simple question though: in these case, is it equally required to  
> > update clients as well? we have both Transport and Node clients  
> > connected to our ES cluster.
> > 
> > Thanks,
> > 
> > On 15 nov, 04:42, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> > 
> > > I applied the fix to the 0.17 branch in any case, btw.
> > > 
> > > On Tue, Nov 15, 2011 at 9:06 AM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote:
> > > 
> > > > At first, I would use 0.17 in production in the next weeks but I will  
> > > > switch to 0.18 as you suggest.
> > > 
> > > > So at the present time, I don't need a new release of 0.17.
> > > 
> > > > Thanks  
> > > > David 😉  
> > > > @dadoonet
> > > 
> > > > Le 15 nov. 2011 à 07:56, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) a écrit :
> > > 
> > > > Hey,
> > > 
> > > > ```
> > > > I posted before as a reply to a thread, but it should be on its
> > > > 
> > > > ```
> > 
> > own
> > 
> > > > thread and notice. A major bug was found in 0.17.x versions and  
> > > > 0.18.x (up  
> > > > to and including 0.18.2): \<  
> > > > [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455)\>  
> > > > [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455). This bug  
> > > > means that under load, with long running search requests, the node can  
> > > > become unresponsive and not handle requests properly.
> > > 
> > > > There is already a fix in master and 0.18 branch, and 0.18.3 will  
> > > > be  
> > > > released either today or tomorrow. Wanted to get feedback if a  
> > > > 0.17.10 with  
> > > > the fix should be released as well. I prefer users who upgrade to  
> > > > upgrade  
> > > > to 0.18 while they are at it, but understand if there is a need for  
> > > > 0.17  
> > > > release.
> > > 
> > > > -shay.banon

---

<div class="post-metadata">

**Author:** ![Frederic](https://avatars.discourse-cdn.com/v4/letter/f/4491bb/32.png) [@Frederic](https://discuss.elastic.co/u/Frederic)\
**Post date:** [November 16, 2011, 2:05pm UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/15 "2011-11-16T14:05:19Z")

</div>

That's great. Thanks a lot Shay

On 16 nov, 07:54, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:

> 0.17.10 has just been released. I want to fix another bug in 0.18 and then  
> release 0.18.3 today.
> 
> On Tue, Nov 15, 2011 at 6:13 PM, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> 
> > One user is enough :), I will release 0.17.10 either tonight or tomorrow.
> 
> > On Tue, Nov 15, 2011 at 5:02 PM, Frederic [focampo...@gmail.com](mailto:focampo...@gmail.com) wrote:
> 
> > > Hi Shay,
> 
> > > Thanks for the update and fix. We would certainly need the 0.17.x fix  
> > > for our systems in production, while I test the upgrade to 0.18 in the  
> > > meantime.
> 
> > > Simple question though: in these case, is it equally required to  
> > > update clients as well? we have both Transport and Node clients  
> > > connected to our ES cluster.
> 
> > > Thanks,
> 
> > > On 15 nov, 04:42, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> > > 
> > > > I applied the fix to the 0.17 branch in any case, btw.
> 
> > > > On Tue, Nov 15, 2011 at 9:06 AM, David Pilato [da...@pilato.fr](mailto:da...@pilato.fr) wrote:
> > > > 
> > > > > At first, I would use 0.17 in production in the next weeks but I will  
> > > > > switch to 0.18 as you suggest.
> 
> > > > > So at the present time, I don't need a new release of 0.17.
> 
> > > > > Thanks  
> > > > > David 😉  
> > > > > @dadoonet
> 
> > > > > Le 15 nov. 2011 à 07:56, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) a écrit :
> 
> > > > > Hey,
> 
> > > > > ```
> > > > > I posted before as a reply to a thread, but it should be on its
> > > > > 
> > > > > ```
> > > 
> > > own
> > > 
> > > > > thread and notice. A major bug was found in 0.17.x versions and  
> > > > > 0.18.x (up  
> > > > > to and including 0.18.2): \<  
> > > > > [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455)\>  
> > > > > [Search: Search requests execute by mistake on the networking http IO thread, causing other http operations to hang · Issue #1455 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/1455). This bug  
> > > > > means that under load, with long running search requests, the node can  
> > > > > become unresponsive and not handle requests properly.
> 
> > > > > There is already a fix in master and 0.18 branch, and 0.18.3 will  
> > > > > be  
> > > > > released either today or tomorrow. Wanted to get feedback if a  
> > > > > 0.17.10 with  
> > > > > the fix should be released as well. I prefer users who upgrade to  
> > > > > upgrade  
> > > > > to 0.18 while they are at it, but understand if there is a need for  
> > > > > 0.17  
> > > > > release.
> 
> > > > > -shay.banon

---

<div class="post-metadata">

**Author:** ![Damien\_Hardy](https://avatars.discourse-cdn.com/v4/letter/d/779978/32.png) [@Damien\_Hardy](https://discuss.elastic.co/u/Damien_Hardy)\
**Post date:** [November 16, 2011, 2:08pm UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/16 "2011-11-16T14:08:24Z")

</div>

Hello,

Any chance having the .deb package directly available for download ?

Thank you for the good working,

--  
Damien

On 16 nov, 07:54, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:

> > 0.17.10 has just been released. I want to fix another bug in 0.18 and  
> > then  
> > release 0.18.3 today.

---

<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:** [November 16, 2011, 5:46pm UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/17 "2011-11-16T17:46:27Z")

</div>

You mean the one that is built as part of elasticsearch since 0.18.x? It  
will be provided as an official download once people will start to use it a  
bit.

On Wed, Nov 16, 2011 at 4:08 PM, Damien Hardy [damienhardy.bal@gmail.com](mailto:damienhardy.bal@gmail.com)wrote:

> Hello,
> 
> Any chance having the .deb package directly available for download ?
> 
> Thank you for the good working,
> 
> --  
> Damien
> 
> On 16 nov, 07:54, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:
> 
> > > 0.17.10 has just been released. I want to fix another bug in 0.18 and  
> > > then  
> > > release 0.18.3 today.

---

<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:48am UTC](https://discuss.elastic.co/t/major-bug-in-0-17-x-and-0-18-x-up-to-0-18-2/5874/18 "2017-07-06T03:48:24Z")

</div>