# Query on elasticsearch installation

**URL:** <https://discuss.elastic.co/t/query-on-elasticsearch-installation/87948>\
**Category:** Elasticsearch\
**Created:** [June 1, 2017, 3:56pm UTC](https://discuss.elastic.co/t/query-on-elasticsearch-installation/87948 "2017-06-01T15:56:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vijayramachandran](https://avatars.discourse-cdn.com/v4/letter/v/858c86/32.png) [@vijayramachandran](https://discuss.elastic.co/u/vijayramachandran)\
**Post date:** [June 1, 2017, 3:56pm UTC](https://discuss.elastic.co/t/query-on-elasticsearch-installation/87948/1 "2017-06-01T15:56:22Z")

</div>

Hello there!

I have got a query on the elasticsearch installation.

We have installed elasticsearch with x-pack using ansible, and the specs are here,

1.) Server A - node 1 (master), node 2 (data node)  
2.) Server B - node 1 (master), node 2 (data node)

How would elasticsearch correspond and sync internally between the nodes when I access the url of node1 and update something on it?

Since x-pack is present, when I create a user using file realm, will it get synced across the nodes? (if I create a user in node 1 called testuser, would it be available and accessible from server A node2, or Server B nodes?

My configuration goes down here,

Server A:

Node 1:  
\> bootstrap.memory\_lock: false  
\> bootstrap.system\_call\_filter: false  
\> [cluster.name](http://cluster.name): custom-cluster  
\> cluster.routing.allocation.disk.threshold\_enabled: true  
\> cluster.routing.allocation.disk.watermark.high: 0.99  
\> cluster.routing.allocation.disk.watermark.low: 0.98  
\> discovery.zen.minimum\_master\_nodes: 1  
\> discovery.zen.ping.unicast.hosts:  
\> - [ccncmu30.de.db.com:9301](http://ccncmu30.de.db.com:9301)  
\> - [ccncmu32.de.db.com:9301](http://ccncmu32.de.db.com:9301)  
\> http.port: 9201  
\> index.codec: best\_compression  
\> network.host: [ccncmu30.de.db.com](http://ccncmu30.de.db.com)  
\> node.data: false  
\> node.master: true  
\> transport.tcp.port: 9301  
\> xpack.security.authc.realms.file1.order: 0  
\> xpack.security.authc.realms.file1.type: file  
\> xpack.security.authc.realms.native1.order: 1  
\> xpack.security.authc.realms.native1.type: native  
\> xpack.security.http.ssl.enabled: true  
\> xpack.security.transport.ssl.enabled: true  
\> xpack.ssl.keystore.key\_password: abcde  
\> xpack.ssl.keystore.password: welcome1  
\> xpack.ssl.keystore.path: /opt/elastic/applications/elasticsearch-5.2.2/node1/x-pack/certs/ccncmu30.de.db.com\_elastic\_uat.jks  
\> xpack.ssl.truststore.password: welcome1

```
> node.name: ccncmu30.de.db.com-node1

> #################################### Paths ####################################

> # Path to directory containing configuration (this file and logging.yml):
> path.conf: /opt/elastic/applications/elasticsearch-5.2.2/node1

> path.data: /opt/elastic/applications/elasticsearch-5.2.2/data/ccncmu30.de.db.com-node1

> path.logs: /opt/elastic/applications/elasticsearch-5.2.2/logs/ccncmu30.de.db.com-node1

> xpack.monitoring.enabled: false

```

node 2:

```
> bootstrap.memory_lock: false
> bootstrap.system_call_filter: false
> cluster.name: custom-cluster
> cluster.routing.allocation.disk.threshold_enabled: true
> cluster.routing.allocation.disk.watermark.high: 0.99
> cluster.routing.allocation.disk.watermark.low: 0.98
> discovery.zen.ping.unicast.hosts:
> - ccncmu30.de.db.com:9301
> - ccncmu32.de.db.com:9301
> http.port: 9202
> index.codec: best_compression
> network.host: ccncmu30.de.db.com
> node.data: true
> node.master: false
> transport.tcp.port: 9302
> xpack.security.authc.realms.file1.order: 0
> xpack.security.authc.realms.file1.type: file
> xpack.security.authc.realms.native1.order: 1
> xpack.security.authc.realms.native1.type: native
> xpack.security.http.ssl.enabled: true
> xpack.security.transport.ssl.enabled: true
> xpack.ssl.keystore.key_password: abc123
> xpack.ssl.keystore.password: welcome1
> xpack.ssl.keystore.path: /opt/elastic/applications/elasticsearch-5.2.2/node2/x-pack/certs/ccncmu30.de.db.com_elastic_uat.jks
> xpack.ssl.truststore.password: welcome1
> xpack.ssl.truststore.path: /opt/elastic/applications/elasticsearch-5.2.2/node2/x-pack/certs/ccncmu30.de.db.com_elastic_uat.jks

```

Similary on server B on node 1 and node 2 the same goes like above.

Please help me on this.

Thanks,

Vijay

---

<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 29, 2017, 3:56pm UTC](https://discuss.elastic.co/t/query-on-elasticsearch-installation/87948/2 "2017-06-29T15:56:27Z")

</div>

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