# Cope with coordination deprecation from Elasticsearch 6.0

**URL:** <https://discuss.elastic.co/t/cope-with-coordination-deprecation-from-elasticsearch-6-0/132844>\
**Category:** Elasticsearch\
**Created:** [May 22, 2018, 3:03pm UTC](https://discuss.elastic.co/t/cope-with-coordination-deprecation-from-elasticsearch-6-0/132844 "2018-05-22T15:03:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hitotsukami](https://avatars.discourse-cdn.com/v4/letter/h/df705f/32.png) [@hitotsukami](https://discuss.elastic.co/u/hitotsukami)\
**Post date:** [May 22, 2018, 3:03pm UTC](https://discuss.elastic.co/t/cope-with-coordination-deprecation-from-elasticsearch-6-0/132844/1 "2018-05-22T15:03:48Z")

</div>

Hi,

I am migrating from Elasticsearch 1.5 to 6.2 on my recommendation system and I am facing some issue regarding the new score computation logic.  
I have opened a question here: [https://stackoverflow.com/questions/50465539/cope-with-coordination-deprecation-from-elasticsearch-6-0](https://stackoverflow.com/questions/50465539/cope-with-coordination-deprecation-from-elasticsearch-6-0)

I also read related discussions on this issue on ES's github but I still cannot figure out a nice solution for Elasticsearch 6.2.  
Could someone give me a feedback?

Thanks

---

<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 19, 2018, 3:03pm UTC](https://discuss.elastic.co/t/cope-with-coordination-deprecation-from-elasticsearch-6-0/132844/2 "2018-06-19T15:03:58Z")

</div>

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