# Failed to register an accepted channel

**URL:** <https://discuss.elastic.co/t/failed-to-register-an-accepted-channel/169156>\
**Category:** Elasticsearch\
**Created:** [February 20, 2019, 8:11am UTC](https://discuss.elastic.co/t/failed-to-register-an-accepted-channel/169156 "2019-02-20T08:11:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pietjepuk](https://avatars.discourse-cdn.com/v4/letter/p/d78d45/32.png) [@pietjepuk](https://discuss.elastic.co/u/pietjepuk)\
**Post date:** [February 20, 2019, 8:11am UTC](https://discuss.elastic.co/t/failed-to-register-an-accepted-channel/169156/1 "2019-02-20T08:11:15Z")

</div>

Hi all,

I'm running into this error message when running extensive queries from a python script and when adding / removing nodes. It seems to occur only when putting elasticsearch "to work". There is no problem when running the normal workload.

My use case:  
I'm logging time series data, one index per day per source.  
Currently we mostly have 4 to 8 sources online at a time.  
The data consists of one document per second, the document contains about 20 metrics that get mapped to int's, doubles, ....  
This setup has been running for about a year, one index is mostly 40 - 60 MB, the total indexes now is 1200, each index has 3 primaries and 2 replica's, total store size is now 210 Gigs (including replica's)

My hardware:  
Now: 3x quad-core vps running on (local)ssd with 16 Gigs of memory of which elastic gets 8.  
previous: 3x quad-core dedicated on spinning disks with the same memory settings.  
Both setups produce the same problem.

The software:  
Elastic 6.5.1 running on ubuntu 18.04 with openjdk 1.8.0\_191, nofile is set to 200000:200000, swap disabled.

2 questions:

1. How do I resolve this error (..duh..) Last time I ran the script the cluster came to a grinding halt and could only recover after rebooting with 5 nodes.. with 3 it crashed before reallocating shards with the same error.

2. What would be a better scheme of saving this data ? Are there to many small indexes now ? Maybe it's better to combine the indexes per week / month / year ?

There is a small portion of the logs here: [https://pastebin.com/Y8ftm6uy](https://pastebin.com/Y8ftm6uy) Please let me know if you require more logs / other data.

Thanx for any insight !!

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [February 20, 2019, 8:50am UTC](https://discuss.elastic.co/t/failed-to-register-an-accepted-channel/169156/2 "2019-02-20T08:50:13Z")

</div>

This is unexpected. I filed a bug report here: [https://github.com/elastic/elasticsearch/issues/39171](https://github.com/elastic/elasticsearch/issues/39171). Please could you introduce yourself on that issue report so we know your Github handle in case we need to ask you some followup questions?

---

<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:** [March 20, 2019, 8:50am UTC](https://discuss.elastic.co/t/failed-to-register-an-accepted-channel/169156/3 "2019-03-20T08:50:16Z")

</div>

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