# Elasticsearch and reliability **URL:** \ **Category:** Elasticsearch\ **Created:** [March 1, 2020, 5:51pm UTC](https://discuss.elastic.co/t/elasticsearch-and-reliability/221589 "2020-03-01T17:51:25Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![dollboot](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@dollboot](https://discuss.elastic.co/u/dollboot)\ **Post date:** [March 1, 2020, 5:51pm UTC](https://discuss.elastic.co/t/elasticsearch-and-reliability/221589/1 "2020-03-01T17:51:25Z")
For a while i've been using Elasticsearch and I have a few questions regarding reliability, replication and ingest processors. I read the following page: [https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-replication.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-replication.html) For this example we have the following setup: 3 Elasticsearch nodes in a cluster (master + data + ingest on every node) 1 Logstash When you send a document to Elasticsearch, with Logstash, it will initially arrive in memory. - What happens if in this exact moment the node, that receives the document, will die? - Even if the connection is TCP is this also on the application level, does this mean that logstash will re-send the message or can it happen that a document will get lost? - How are ingest processors implemented, before or after replication? - When an ingest node dies could there be a possibility that a received document will be lost, or does Logstash just resend the document? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 29, 2020, 5:51pm UTC](https://discuss.elastic.co/t/elasticsearch-and-reliability/221589/2 "2020-03-29T17:51:26Z")
Closed on March 29, 2020, 5:51pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.