# Creating dedicated master nodes. How do we turn off coordinating responsibilities for master nodes? **URL:** \ **Category:** Elasticsearch\ **Created:** [March 26, 2020, 12:11am UTC](https://discuss.elastic.co/t/creating-dedicated-master-nodes-how-do-we-turn-off-coordinating-responsibilities-for-master-nodes/225087 "2020-03-26T00:11:21Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![hhsuey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hhsuey/32/45013_2.png) [@hhsuey](https://discuss.elastic.co/u/hhsuey)\ **Post date:** [March 26, 2020, 12:11am UTC](https://discuss.elastic.co/t/creating-dedicated-master-nodes-how-do-we-turn-off-coordinating-responsibilities-for-master-nodes/225087/1 "2020-03-26T00:11:22Z")
Here it is stated that the master node should not be a coordinating node. > Dedicated master-eligible nodes only have the `master` role, allowing them to focus on managing the cluster. While master nodes can also behave as [coordinating nodes](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#coordinating-node) and route search and indexing requests from clients to data nodes, it is better _not_ to use dedicated master nodes for this purpose. However, we then state that every node is implicitly a coordinating node, and suggest that cannot be disabled: > Every node is implicitly a coordinating node. This means that a node that has all three `node.master` , `node.data` and `node.ingest` set to `false` will only act as a coordinating node, **which cannot be disabled.** > **[Node | Elasticsearch Guide \[8.11\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#dedicated-master-node)** Is it possible to turn off coordinating node responsibilities? Or is it acceptable to have master nodes also be coordinating nodes? ---
**Author:** ![wangqinghuan](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@wangqinghuan](https://discuss.elastic.co/u/wangqinghuan)\ **Post date:** [March 26, 2020, 3:44am UTC](https://discuss.elastic.co/t/creating-dedicated-master-nodes-how-do-we-turn-off-coordinating-responsibilities-for-master-nodes/225087/2 "2020-03-26T03:44:31Z")
Welcome hhsuey! As docs said, I don't think coordinating responsibilities can be disabled . If you want prohibit user connect to master node, you can add a http proxy in front of cluster to limit user's access some dedicated master nodes. ---
**Author:** ![hhsuey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hhsuey/32/45013_2.png) [@hhsuey](https://discuss.elastic.co/u/hhsuey)\ **Post date:** [March 26, 2020, 4:23am UTC](https://discuss.elastic.co/t/creating-dedicated-master-nodes-how-do-we-turn-off-coordinating-responsibilities-for-master-nodes/225087/3 "2020-03-26T04:23:26Z")
Thanks! So basically, if we stop client access to the master nodes, they will not be able to perform any coordinating node functions? ---
**Author:** ![wangqinghuan](https://avatars.discourse-cdn.com/v4/letter/w/d26b3c/32.png) [@wangqinghuan](https://discuss.elastic.co/u/wangqinghuan)\ **Post date:** [March 26, 2020, 5:08am UTC](https://discuss.elastic.co/t/creating-dedicated-master-nodes-how-do-we-turn-off-coordinating-responsibilities-for-master-nodes/225087/4 "2020-03-26T05:08:05Z")
Yes,responsibility of coordinating node is forward request to data nodes and reduce data nodes' data. If not access coordinating nodes, they will not receive request. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 23, 2020, 5:08am UTC](https://discuss.elastic.co/t/creating-dedicated-master-nodes-how-do-we-turn-off-coordinating-responsibilities-for-master-nodes/225087/5 "2020-04-23T05:08:37Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.