# How to elude error \[can't select channel size is 0 for types\]?

**URL:** <https://discuss.elastic.co/t/how-to-elude-error-cant-select-channel-size-is-0-for-types/130935>\
**Category:** Elasticsearch\
**Created:** [May 8, 2018, 5:41am UTC](https://discuss.elastic.co/t/how-to-elude-error-cant-select-channel-size-is-0-for-types/130935 "2018-05-08T05:41:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [May 8, 2018, 5:41am UTC](https://discuss.elastic.co/t/how-to-elude-error-cant-select-channel-size-is-0-for-types/130935/1 "2018-05-08T05:41:48Z")

</div>

Hello.

I have came across below error while creating _index pattern_ through kibana UI. I would appreciate if I could get some help to elude the error.

```
[2018-05-08T05:23:16,981][WARN][r.suppressed] path: /.kibana/doc/index-pattern%3Ae9aaa8c0-527f-11e8-a6f6-9bf083f4f01a, params: {refresh=wait_for, index=.kibana, id=index-pattern:e9aaa8c0-527f-11e8-a6f6-9bf083f4f01a, type=doc}
org.elasticsearch.transport.SendRequestTransportException: [es-d1][10.146.0.4:9300][indices:data/write/bulk[s]]
        at org.elasticsearch.transport.TransportService.sendRequestInternal(TransportService.java:608) ~[elasticsearch-6.2.4.jar:6.2.4]
        at org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:518) ~[elasticsearch-6.2.4.jar:6.2.4]
        at org.elasticsearch.transport.TransportService.sendRequest(TransportService.java:506) ~[elasticsearch-6.2.4.jar:6.2.4]

....
Caused by: java.lang.IllegalStateException: can't select channel size is 0 for types: [RECOVERY, BULK, STATE]
        at org.elasticsearch.transport.ConnectionProfile$ConnectionTypeHandle.getChannel(ConnectionProfile.java:213) ~[elasticsearch-6.2.4.jar:6.2.4]
        at org.elasticsearch.transport.TcpTransport$NodeChannels.channel(TcpTransport.java:433) ~[elasticsearch-6.2.4.jar:6.2.4]
        at org.elasticsearch.transport.TcpTransport$NodeChannels.sendRequest(TcpTransport.java:481) ~[elasticsearch-6.2.4.jar:6.2.4]
        at org.elasticsearch.transport.TransportService.sendRequestInternal(TransportService.java:598) ~[elasticsearch-6.2.4.jar:6.2.4]
        ... 79 more

```

### ENVIRONMENT

kibana 6.2.4  
elasticsearch 6.2.4

I have two clusters with below nodes.

Cluster : mycluster1 , m: master node , d : data node, con : coordinating-only-node

```
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
10.146.0.3 8 55 3 0.05 0.08 0.07 m * es-m1
10.146.0.4 9 59 5 0.11 0.09 0.07 d - es-d1
10.146.0.7 8 67 2 0.14 0.08 0.07 - - es-con-2
10.146.0.2 8 61 4 0.07 0.05 0.05 - - es-con

```

Cluster : mycluster2

```
ip heap.percent ram.percent cpu load_1m load_5m load_15m node.role master name
10.146.0.6 9 59 5 0.10 0.11 0.08 di - es-d2
10.146.0.5 8 59 3 0.04 0.08 0.07 m * es-m2

```

### HOW TO REPRODUCE

1.Set _cross cluster search setting_ inside _elasticsearch.yml_ of **coordinating-only-node**. And startup the node.

```
search:
  remote:
    mycluster1:
      seeds: ["10.146.0.4:9300"]
    mycluster2:
      seeds: ["10.146.0.6:9300"]

```

2.From _kibana UI_ , create _index\_pattern_ . Click **Create index pattern**.

![capture-1](https://us1.discourse-cdn.com/elastic/original/3X/7/7/77b02d42f80134932304d4a23431c55704d24f49.PNG)

### QUESTION

I believe this problem is related to below incident. However, I was able to elude this by setting _cross cluster search_ from _cluster setting API (Persistent)_ .

> <https://github.com/elastic/elasticsearch/issues/29321>

So , my question is should I set the _cross cluster search_ by using **cluster setting API** for now to elude the error ?

---

<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:** [June 5, 2018, 5:41am UTC](https://discuss.elastic.co/t/how-to-elude-error-cant-select-channel-size-is-0-for-types/130935/2 "2018-06-05T05:41:51Z")

</div>

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