# How auto-sync happens within multiple nodes in an ES cluster without ES restart? **URL:** \ **Category:** Elasticsearch\ **Created:** [June 12, 2014, 3:15pm UTC](https://discuss.elastic.co/t/how-auto-sync-happens-within-multiple-nodes-in-an-es-cluster-without-es-restart/18071 "2014-06-12T15:15:12Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![nishidha\_randad](https://avatars.discourse-cdn.com/v4/letter/n/c68b51/32.png) [@nishidha\_randad](https://discuss.elastic.co/u/nishidha_randad)\ **Post date:** [June 12, 2014, 3:15pm UTC](https://discuss.elastic.co/t/how-auto-sync-happens-within-multiple-nodes-in-an-es-cluster-without-es-restart/18071/1 "2014-06-12T15:15:12Z")
Hello, We need to understand data synchronization between various nodes in a cluster without restarting ES nodes. Let's say, ES cluster has 3 nodes, if one is updated, how data in other two nodes is synced with the change? Also, if say one node is down, how that node gets updated data from other nodes after it gets up? Also, how a node from a cluster is chosen when ES read/write query is fired? Thanks, Nishidha -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/85d48661-a03f-48d8-943b-66855336b2b6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/85d48661-a03f-48d8-943b-66855336b2b6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:23am UTC](https://discuss.elastic.co/t/how-auto-sync-happens-within-multiple-nodes-in-an-es-cluster-without-es-restart/18071/2 "2017-07-06T01:23:00Z")