# 6.1.1 histogram aggregation crashes and stops elasticsearch

**URL:** <https://discuss.elastic.co/t/6-1-1-histogram-aggregation-crashes-and-stops-elasticsearch/157452>\
**Category:** Elasticsearch\
**Created:** [November 19, 2018, 10:29pm UTC](https://discuss.elastic.co/t/6-1-1-histogram-aggregation-crashes-and-stops-elasticsearch/157452 "2018-11-19T22:29:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![linkerc](https://avatars.discourse-cdn.com/v4/letter/l/13edae/32.png) [@linkerc](https://discuss.elastic.co/u/linkerc)\
**Post date:** [November 19, 2018, 10:29pm UTC](https://discuss.elastic.co/t/6-1-1-histogram-aggregation-crashes-and-stops-elasticsearch/157452/1 "2018-11-19T22:29:11Z")

</div>

I'm experiencing "histogram" aggregation crashing 6.1.1 consistently. But I can't seem to find a bug relating to my observation.  
The closest I can find are a couple on 6.0.0.  
I'm wondering if anybody has experience similar crashes.  
The crash log only shows closed connection, so it might be logging the result of the crash.

java.nio.channels.ClosedChannelException: null  
at io.netty.channel.AbstractChannel$AbstractUnsafe.write(...)(Unknown Source) ~[?:?]  
[2018-11-19T21:33:14,842][DEBUG][o.e.a.a.i.g.TransportGetIndexAction] [es-access-000] no known master node, scheduling a retry  
[2018-11-19T21:33:14,848][DEBUG][o.e.a.a.i.g.TransportGetIndexAction] [es-access-000] no known master node, scheduling a retry  
[2018-11-19T21:33:14,975][INFO][o.e.c.s.ClusterApplierService] [es-access-000] detected\_master {es-access-001}{EHi7qn7XQXe2M\_xpN-MZaQ}{GrLXhBHNTi-3EbTJvd1Ggg}{172.31.25.158}{172.31.25.158:9300}, reason: apply cluster state (from master [master {es-access-001}{EHi7qn7XQXe2M\_xpN-MZaQ}{GrLXhBHNTi-3EbTJvd1Ggg}{172.31.25.158}{172.31.25.158:9300} committed version [162517]])

My aggregation is simply "histogram" on a date field. Using "date\_histogram" seems fine.  
_ **"aggs": {** _  
_\*\* "term": {\*\*_  
_\*\* "histogram": {\*\*_  
_\*\* "field": "When",\*\*_  
_\*\* "interval": "1d"\*\*_  
_\*\* }\*\*_  
_\*\* }\*\*_  
_\*\* }\*\*_

This command is issued via kibana.  
I saw few \_tasks were running for more than several minutes by issuing the command  
"GET \_cat/tasks?v".  
Then elasticsearch dies and exits. I had to restart the service to bring it back up.  
Any pointers? I'm hoping it's a resolved issue, hence looking into release notes. But this particular crash seems different than the ones logged. Any insights?  
Thanks in advance.

---

<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:** [December 17, 2018, 10:29pm UTC](https://discuss.elastic.co/t/6-1-1-histogram-aggregation-crashes-and-stops-elasticsearch/157452/2 "2018-12-17T22:29:17Z")

</div>

Closed on December 17, 2018, 10:29pm UTC

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.