# Question about node attribute metadata

**URL:** <https://discuss.elastic.co/t/question-about-node-attribute-metadata/69857>\
**Category:** Elasticsearch\
**Created:** [December 23, 2016, 1:31am UTC](https://discuss.elastic.co/t/question-about-node-attribute-metadata/69857 "2016-12-23T01:31:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ginger](https://avatars.discourse-cdn.com/v4/letter/g/34f0e0/32.png) [@ginger](https://discuss.elastic.co/u/ginger)\
**Post date:** [December 23, 2016, 1:31am UTC](https://discuss.elastic.co/t/question-about-node-attribute-metadata/69857/1 "2016-12-23T01:31:14Z")

</div>

Hi.

I recently use node attribute metadata to achieve [Shard Allocation Awareness](https://www.elastic.co/guide/en/elasticsearch/reference/5.1/allocation-awareness.html). But whenever I need to update those node attribute, I have to restart a node.

In my opinion, all the node attributes is reported to master and stored in the global cluster state. After this, the master node can use those node attributes to achieve shard allocation awareness. If I understand correctly, why not update node attributes through restful API, which will make attribute update operation more elegant.

I want to learn more about the design consideration.

I hope I explain clearly my question, and any help is appreciated.

---

<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:** [January 20, 2017, 1:31am UTC](https://discuss.elastic.co/t/question-about-node-attribute-metadata/69857/2 "2017-01-20T01:31:31Z")

</div>

Closed on January 20, 2017, 1:31am UTC

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