# Using embedded node client in 2.2.0

**URL:** <https://discuss.elastic.co/t/using-embedded-node-client-in-2-2-0/47058>\
**Category:** Elasticsearch\
**Created:** [April 12, 2016, 1:19am UTC](https://discuss.elastic.co/t/using-embedded-node-client-in-2-2-0/47058 "2016-04-12T01:19:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mkelkar](https://avatars.discourse-cdn.com/v4/letter/m/ea666f/32.png) [@mkelkar](https://discuss.elastic.co/u/mkelkar)\
**Post date:** [April 12, 2016, 1:19am UTC](https://discuss.elastic.co/t/using-embedded-node-client-in-2-2-0/47058/1 "2016-04-12T01:19:10Z")

</div>

Hi All,  
We use embedded client node to send/receive data from elasticsearch for a while. I am trying to upgrade to ES 2.2.0, and when using bulk indexing requests I get tons of these exceptions in the log -

ProcessClusterEventTimeoutException[failed to process cluster event (put-mapping [entity]) within 30s]  
at org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:343)  
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

If I check the master node logs, it lists pending nodes which are always my embedded node client IPs....

Also, I see that there are way too many put\_mapping tasks piling up....

Is it a good idea to embed node client in your jvm with 2.2.0? what has changed between ES 1.7.X to 2.2 that may cause this behavior? Should I switch to using transport client instead? Please advice.

Thanks,  
Madhav.

---

<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:** [July 5, 2017, 11:00pm UTC](https://discuss.elastic.co/t/using-embedded-node-client-in-2-2-0/47058/2 "2017-07-05T23:00:29Z")

</div>

Closed on July 5, 2017, 11:00pm UTC