# Elasticsearch Read from Multiple Locations **URL:** \ **Category:** Elasticsearch\ **Created:** [April 2, 2019, 11:52am UTC](https://discuss.elastic.co/t/elasticsearch-read-from-multiple-locations/174980 "2019-04-02T11:52:06Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![SISA\_Nirmal\_kumar\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sisa_nirmal_kumar_b/32/43304_2.png) [@SISA\_Nirmal\_kumar\_B](https://discuss.elastic.co/u/SISA_Nirmal_kumar_B)\ **Post date:** [April 2, 2019, 11:52am UTC](https://discuss.elastic.co/t/elasticsearch-read-from-multiple-locations/174980/1 "2019-04-02T11:52:06Z")
Is it possible to configure elasticsearch to read data from multiple locations / path ? ---
**Author:** ![SISA\_Nirmal\_kumar\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sisa_nirmal_kumar_b/32/43304_2.png) [@SISA\_Nirmal\_kumar\_B](https://discuss.elastic.co/u/SISA_Nirmal_kumar_B)\ **Post date:** [April 2, 2019, 12:01pm UTC](https://discuss.elastic.co/t/elasticsearch-read-from-multiple-locations/174980/2 "2019-04-02T12:01:23Z")
My architecture is as below Logstash -\> Elasticsearch (D:\elasticdata) -\> Kibana Expected Architecture Logstash -\> Elasticsearch (D:\elasticdata & E:\elasticdata) Is it possible for Kibana to be able to fetch data from both partition (D and E drive) or Is there any attribute that can be used to set two different path for storing elasticdata and reading the same ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 2, 2019, 3:21pm UTC](https://discuss.elastic.co/t/elasticsearch-read-from-multiple-locations/174980/3 "2019-04-02T15:21:38Z")
Yes, [`path.data` accepts a list of paths](https://www.elastic.co/guide/en/elasticsearch/reference/current/path-settings.html). If you need more control you can run two nodes, one on each path. ---
**Author:** ![SISA\_Nirmal\_kumar\_B](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sisa_nirmal_kumar_b/32/43304_2.png) [@SISA\_Nirmal\_kumar\_B](https://discuss.elastic.co/u/SISA_Nirmal_kumar_B)\ **Post date:** [April 2, 2019, 7:04pm UTC](https://discuss.elastic.co/t/elasticsearch-read-from-multiple-locations/174980/4 "2019-04-02T19:04:04Z")
Thanks for the info David. But my actual query is that currently my elasticsearch is configured to store data in D:\elasticdata but due to space constraints i want to change the path to E:\elasticdata So is it possible for me to configure elasticsearch in such a manner that after changing the path.data to E:\elasticdata, will kibana be able to read data that is stored in D:\elasticdata as well as data that will be stored in E:\elasticdata at the same time ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [April 3, 2019, 7:40am UTC](https://discuss.elastic.co/t/elasticsearch-read-from-multiple-locations/174980/5 "2019-04-03T07:40:03Z")
Sorry, I don't understand the question, or rather I don't understand how else to answer it. If you want Elasticsearch to use both paths then either add both paths to `path.data` or else run two nodes, one on each path. If you want to use _only_ `E:\elasticdata` then you can shut down Elasticsearch and move the directory from `D:\` to `E:\`, then adjust `path.data` and restart Elasticsearch. But there's no way for Kibana to read data from a data path that is different from Elasticsearch's `path.data`, because Kibana doesn't read data directly, it only reads things via Elasticsearch. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [May 1, 2019, 7:40am UTC](https://discuss.elastic.co/t/elasticsearch-read-from-multiple-locations/174980/6 "2019-05-01T07:40:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.