# Write and Query on Elasticsearch

**URL:** <https://discuss.elastic.co/t/write-and-query-on-elasticsearch/59761>\
**Category:** Elasticsearch\
**Created:** [September 4, 2016, 3:23pm UTC](https://discuss.elastic.co/t/write-and-query-on-elasticsearch/59761 "2016-09-04T15:23:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![userguy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/userguy/32/6224_2.png) [@userguy](https://discuss.elastic.co/u/userguy)\
**Post date:** [September 4, 2016, 3:23pm UTC](https://discuss.elastic.co/t/write-and-query-on-elasticsearch/59761/1 "2016-09-04T15:23:23Z")

</div>

I have Setup where around 100mn logs lines are written in elasticsearch with help of logstash and same setup is used in kibana for search and dashboard ..

How should i configure so that neither search nor indexing (optimize) gets affected .

Does any one has any tested number or configurational parameters keeping indexing and searching in mind

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 5, 2016, 6:44am UTC](https://discuss.elastic.co/t/write-and-query-on-elasticsearch/59761/2 "2016-09-05T06:44:00Z")

</div>

This is why you scale 🙂

---

<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:** [July 5, 2017, 10:22pm UTC](https://discuss.elastic.co/t/write-and-query-on-elasticsearch/59761/3 "2017-07-05T22:22:33Z")

</div>

Closed on July 5, 2017, 10:22pm UTC