Trying to understand the following scenarios of consistency in elasticsearch:
1) sync replication - How does elasticsearch deals with consistency issue that may arise from 1 node momentarily going down and missing writes to it? When the node comes backup and the reads going to the non-primary shards could get inconsistent data? 2) async replication - What happens if replication is slow for some reason, could users see inconsistent data? 3) sync/async replication - how does elasticsearch keep data in sync for those writes that never happened on the non-primary shard because of network/node failures? -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAOT3TWrpUEpVU2yg3km_v%3DtuA0duSiFV5HYnPyeCztdmrTcMsA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
