# Remote cluster node query

**URL:** https://discuss.elastic.co/t/remote-cluster-node-query/341033
**Category:** Elasticsearch
**Created:** [August 17, 2023, 4:49pm UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033 "2023-08-17T16:49:53Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)
#### Post date: [August 17, 2023, 4:49pm UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033/1 "2023-08-17T16:49:53Z")

</div>

We have an existing elasticsearch stack running basic license, is it possible to add more nodes to the cluster which do not hold any data and only pass data from a location to existing data / master nodes with basic license?

I read somewhere that if nodes are added to same cluster then remote cluster is not applicable, to clarify my proposed nodes are in different datacenter however will be sending data to existing cluster.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [August 17, 2023, 6:05pm UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033/2 "2023-08-17T18:05:23Z")

</div>

As long as they are part of the same cluster, yes you can.

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [August 17, 2023, 6:21pm UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033/3 "2023-08-17T18:21:28Z")

</div>

Hi @Atul_Chadha

Let's clarify a bit

Local and Remote is in reference to clusters.. a local cluster and a remote cluster.

Nodes are always within a single cluster, there is no concept of local / remote nodes.

---

<div class="post-metadata">

### Author: ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)
#### Post date: [August 17, 2023, 11:23pm UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033/4 "2023-08-17T23:23:38Z")

</div>

Okay, could you advise what node type i should be using for nodes in datacenter B (currently whole els setup is in Datacenter A). I need these new nodes to be just adding data to existing setup and not store anything locally in datacenter B

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [August 18, 2023, 4:45am UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033/5 "2023-08-18T04:45:54Z")

</div>

In general I would not recommend splitting a cluster across data centers generally that is not considered best practice and can result in an unstable cluster.

It is possible to do this but you need guaranteed low latency... And solid connectivity.

Personally I do not recommend but it is possible and some users do it.

> [@Atul\_Chadha](#):
>
> I need these new nodes to be just adding data to existing setup and not store anything locally in datacenter B

A little confused by this but sound like you are describing a coordinating role only... Which only accepts queries and index requests but stores no data.

But why not just send the request directly from data center B to the cluster in Data center A... In the first place?

---

<div class="post-metadata">

### Author: ![Atul\_Chadha](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/atul_chadha/32/75469_2.png) [@Atul\_Chadha](https://discuss.elastic.co/u/Atul_Chadha)
#### Post date: [August 18, 2023, 5:11am UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033/6 "2023-08-18T05:11:16Z")

</div>

I am trying to avoid multiple servers trying to connect to existing elastic in DC A and allow 1 more elastic node ( which should only consolidate and pass on request to existing stack ).

This way its easier to allow communication on 1 node rather than multiple nodes trying to connect across different DC

---

<div class="post-metadata">

### Author: ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)
#### Post date: [August 18, 2023, 5:18am UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033/7 "2023-08-18T05:18:41Z")

</div>

Sounds like a good use case for a normal proxy... That is exactly what a proxy does... Forward request from many source through a single egress point.

But you can certainly go ahead and give the node in the data center B a try..

---

<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: [September 15, 2023, 5:18am UTC](https://discuss.elastic.co/t/remote-cluster-node-query/341033/8 "2023-09-15T05:18:51Z")

</div>

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