# Single node cluster in production, any suggestion?

**URL:** <https://discuss.elastic.co/t/single-node-cluster-in-production-any-suggestion/148281>\
**Category:** Elasticsearch\
**Created:** [September 12, 2018, 8:44am UTC](https://discuss.elastic.co/t/single-node-cluster-in-production-any-suggestion/148281 "2018-09-12T08:44:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![arota](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arota/32/35423_2.png) [@arota](https://discuss.elastic.co/u/arota)\
**Post date:** [September 12, 2018, 8:44am UTC](https://discuss.elastic.co/t/single-node-cluster-in-production-any-suggestion/148281/1 "2018-09-12T08:44:48Z")

</div>

Hello, I am about using Elasticsearch as component of a standalone application, running on a single node. The application will run on a pretty decent dedicated consumer machine (i7 7xxx/2c/4t, 16/32 gb of RAM, pcie SSD), running Linux.

Elasticsearch is used for:

- secondary data store (300K small documents of less than 1 KB each a day)
- analytics (a couple of aggregations used by the application to computer some KPI every hour or so, performances are good so far)

Hardware/software failures are not critical: downtimes and partial data losses are tollerated.

What are best practices/suggestions/points to consider?

---

<div class="post-metadata">

**Author:** ![jaddison](https://avatars.discourse-cdn.com/v4/letter/j/e5b9ba/32.png) [@jaddison](https://discuss.elastic.co/u/jaddison)\
**Post date:** [September 12, 2018, 5:11pm UTC](https://discuss.elastic.co/t/single-node-cluster-in-production-any-suggestion/148281/2 "2018-09-12T17:11:58Z")

</div>

I do something very similar but spread out over 3 AWS t2 instances (our system load is not that intense). Web server, database server (postgresql), and search server (elasticsearch). The reason for this setup is so that you can allocate and lock system memory for elasticsearch, without affecting other processes.

My systems have far more modest amounts of RAM, so you might be able to get away with allocating/locking a portion of that 32GB memory for elasticsearch. Regardless, memory and IO would be top of mind for a single node ES configuration.

---

<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:** [October 10, 2018, 5:12pm UTC](https://discuss.elastic.co/t/single-node-cluster-in-production-any-suggestion/148281/3 "2018-10-10T17:12:09Z")

</div>

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