Broker Responding twice to large groupBy Query

Hi,

I am having a very odd issue in that our Druid Broker is responding twice(same data each time) when I make a very large request. The exact same query works consistently up to fairly large data sets but it seems to cross a threshold where it starts returning twice which as you can imagine really messes things up. I have done extensive trouble-shooting to make sure this is actually happening and not just an oversight in my code. I am making the request from a nodejs server and have even tried using different modules to rule out any problems there. I would very much prefer to actually get to the root of this problem rather than just working around it. We are currently running 0.10.1 on production. My apologies if this is an existing issue I could not find anything myself.

To make things weirder they seem to be responding in different formats but as i said with the same data.

The first one that returns is always as I would expect:

{

“req”: {

“method”: “POST”,

“url”: “http://broker-ip:8082/druid/v2”,

“data”: “queryJSON”,

“headers”: {

“user-agent”: “node-superagent/3.8.1”,

“content-type”: “application/json”,

“connection”: “keep-alive”

}

},

“header”: {

“date”: “Mon, 11 Dec 2017 18:15:42 GMT”,

“content-type”: “application/json”,

“x-druid-query-id”: “76c50c8c-c7cd-40db-937f-ec958259a68e”,

“x-druid-response-context”: “{}”,

“vary”: “Accept-Encoding, User-Agent”,

“content-encoding”: “gzip”,

“transfer-encoding”: “chunked”,

“server”: “Jetty(9.3.19.v20170502)”

},

“status”: 200,

“text”: “Response Data…”

}

The second response always comes through the err field:

{

“response”: {

“req”: {

“method”: “POST”,

“url”: “http://broker-ip:8082/druid/v2”,

“data”: “queryJSON”,

“headers”: {

“user-agent”: “node-superagent/3.8.1”,

“content-type”: “application/json”,

“connection”: “keep-alive”

}

},

“header”: {

“date”: “Mon, 11 Dec 2017 18:15:42 GMT”,

“content-type”: “application/json”,

“x-druid-query-id”: “76c50c8c-c7cd-40db-937f-ec958259a68e”,

“x-druid-response-context”: “{}”,

“vary”: “Accept-Encoding, User-Agent”,

“content-encoding”: “gzip”,

“transfer-encoding”: “chunked”,

“server”: “Jetty(9.3.19.v20170502)”

},

“status”: 200,

“text”: “Response Data…”

}

}

I would greatly appreciate any help I am real stumped on this one. This definitely seems like a potential bug to me.

Regards,

Josh