# Coordinating Node do not forward X-Opaque-ID header

**URL:** <https://discuss.elastic.co/t/coordinating-node-do-not-forward-x-opaque-id-header/222078>\
**Category:** Elasticsearch\
**Created:** [March 4, 2020, 1:01pm UTC](https://discuss.elastic.co/t/coordinating-node-do-not-forward-x-opaque-id-header/222078 "2020-03-04T13:01:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GabrielM](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabrielm/32/47827_2.png) [@GabrielM](https://discuss.elastic.co/u/GabrielM)\
**Post date:** [March 4, 2020, 1:01pm UTC](https://discuss.elastic.co/t/coordinating-node-do-not-forward-x-opaque-id-header/222078/1 "2020-03-04T13:01:28Z")

</div>

Hello, I am pretty sure that the coordinating nodes of a cluster do not forward the X-Opaque-ID header to the data nodes.

So if you are using coordinating nodes in a cluster, you can not identify running tasks ([https://www.elastic.co/guide/en/elasticsearch/reference/master/tasks.html#\_identifying\_running\_tasks](https://www.elastic.co/guide/en/elasticsearch/reference/master/tasks.html#_identifying_running_tasks)) ?

Thank you in advance, have a nice day.

---

<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:** [April 1, 2020, 1:14pm UTC](https://discuss.elastic.co/t/coordinating-node-do-not-forward-x-opaque-id-header/222078/2 "2020-04-01T13:14:55Z")

</div>

Closed on April 1, 2020, 1:14pm UTC

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