# Transport response handler not found of
**URL:** https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808
**Category:** Elasticsearch
**Created:** [October 12, 2016, 1:10pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808 "2016-10-12T13:10:20Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@caecilie](https://discuss.elastic.co/u/caecilie)
#### Post date: [October 12, 2016, 1:10pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808/1 "2016-10-12T13:10:20Z")
I have two server, both with logstash 2.4.0 and elasticsearch 2.4.0. I found the following warnings in the elasticsearch log on my master node:
> ```
> [2016-10-12 14:34:33,957][INFO][cluster.metadata] [node-2] [filebeat-test-2016.10.12] creating index, cause [auto(bulk api)], templates [], shards [5]/[1], mappings []
> [2016-10-12 14:34:34,234][INFO][cluster.routing.allocation] [node-2] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[filebeat-test-2016.10.12][3], [filebeat-test-2016.10.12][1], [filebeat-test-2016.10.12][4], [filebeat-test-2016.10.12][0], [filebeat-test-2016.10.12][2]] ...]).
> [2016-10-12 14:34:34,620][INFO][cluster.metadata] [node-2] [filebeat-test-2016.10.12] create_mapping [filebeat-test]
> [2016-10-12 14:34:35,520][INFO][cluster.routing.allocation] [node-2] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[filebeat-test-2016.10.12][4]] ...]).
>
> ```
On my data node I can see nearly at the same time:
> ```
> [2016-10-12 14:34:34,485][WARN][transport] [node-1] Transport response handler not found of id [877575]
> [2016-10-12 14:34:34,495][WARN][transport] [node-1] Transport response handler not found of id [877576]
> [2016-10-12 14:34:35,195][WARN][transport] [node-1] Transport response handler not found of id [877599]
>
> ```
Can someone explain, what happened here?
---
### Author:  [@cbuescher](https://discuss.elastic.co/u/cbuescher)
#### Post date: [October 12, 2016, 1:17pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808/2 "2016-10-12T13:17:44Z")
> [@caecilie](#):
>
> Transport response handler not found of id
This might be a known issue in 2.4.0 that according to [Don't send exception responses twice by imotov · Pull Request #20585 · elastic/elasticsearch · GitHub](https://github.com/elastic/elasticsearch/pull/20585) should be fixed in 2.4.1. Can you try and test with that version?
---
### Author:  [@caecilie](https://discuss.elastic.co/u/caecilie)
#### Post date: [October 12, 2016, 1:54pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808/3 "2016-10-12T13:54:12Z")
After update, no log entries on the data node, but no change on the master node:
> ```
> [2016-10-12 15:49:53,324][INFO][cluster.metadata] [node-2] [filebeat-test-2016.10.12] creating index, cause [auto(bulk api)], templates [], shards [5]/[1], mappings []
> [2016-10-12 15:49:53,565][INFO][cluster.routing.allocation] [node-2] Cluster health status changed from [RED] to [YELLOW] (reason: [shards started [[filebeat-test-2016.10.12][2], [filebeat-test-2016.10.12][0], [filebeat-test-2016.10.12][4], [filebeat-test-2016.10.12][1], [filebeat-test-2016.10.12][3]] ...]).
> [2016-10-12 15:49:54,073][INFO][cluster.metadata] [node-2] [filebeat-test-2016.10.12] create_mapping [filebeat-test]
> [2016-10-12 15:49:54,263][INFO][cluster.routing.allocation] [node-2] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[filebeat-test-2016.10.12][3], [filebeat-test-2016.10.12][1]] ...]).
>
> ```
---
### Author:  [@cbuescher](https://discuss.elastic.co/u/cbuescher)
#### Post date: [October 12, 2016, 2:02pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808/4 "2016-10-12T14:02:33Z")
That looks normal though, see - for example - this [explanation about the cluster health status](https://www.elastic.co/guide/en/elasticsearch/guide/current/_cluster_health.html).
---
### Author:  [@ywelsch](https://discuss.elastic.co/u/ywelsch)
#### Post date: [October 12, 2016, 2:03pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808/5 "2016-10-12T14:03:21Z")
These log lines are **info** rming you (hence logging level INFO) that a new index has been created. It's not a warning. Nothing to worry about.
---
### Author:  [@caecilie](https://discuss.elastic.co/u/caecilie)
#### Post date: [October 12, 2016, 2:21pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808/6 "2016-10-12T14:21:39Z")
Oh thanks, I was confused, because the cluster state was red and I associated red=error 🙂
---
### Author:  [@ywelsch](https://discuss.elastic.co/u/ywelsch)
#### Post date: [October 12, 2016, 2:24pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808/7 "2016-10-12T14:24:55Z")
Index creation makes the cluster red for a very short moment (until shards are started and ready for indexing). In v5.0.0 we have changed this to make it more user-friendly (see here: [https://github.com/elastic/elasticsearch/pull/19450](https://github.com/elastic/elasticsearch/pull/19450) ).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:13pm UTC](https://discuss.elastic.co/t/transport-response-handler-not-found-of/62808/8 "2017-07-05T22:13:02Z")