# Per index path.data setting possible? **URL:** \ **Category:** Elasticsearch\ **Created:** [June 13, 2012, 9:23am UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075 "2012-06-13T09:23:13Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Niklas\_Therning](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niklas_therning/32/2847_2.png) [@Niklas\_Therning](https://discuss.elastic.co/u/Niklas_Therning)\ **Post date:** [June 13, 2012, 9:23am UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075/1 "2012-06-13T09:23:13Z")
Hi, Is it possible to set path.data per index? We would like to store one index on a dedicated SSD while other indexes will be stored on slower HDDs. /Niklas ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [June 14, 2012, 9:09pm UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075/2 "2012-06-14T21:09:10Z")
No, its not possible, though it makes sense. Shouldn't be too difficult to add, just requires thinking on how to expose it. On Wed, Jun 13, 2012 at 11:23 AM, Niklas Therning [niklas@therning.org](mailto:niklas@therning.org)wrote: > Hi, > > Is it possible to set path.data per index? We would like to store one > index on a dedicated SSD while other indexes will be stored on slower HDDs. > > /Niklas ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [June 14, 2012, 9:09pm UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075/3 "2012-06-14T21:09:31Z")
Also, open an issue? On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > No, its not possible, though it makes sense. Shouldn't be too difficult to > add, just requires thinking on how to expose it. > > On Wed, Jun 13, 2012 at 11:23 AM, Niklas Therning [niklas@therning.org](mailto:niklas@therning.org)wrote: > > > Hi, > > > > Is it possible to set path.data per index? We would like to store one > > index on a dedicated SSD while other indexes will be stored on slower HDDs. > > > > /Niklas ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [June 14, 2012, 9:27pm UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075/4 "2012-06-14T21:27:23Z")
One more thing, you can have SSDs on some machines, and disks on others, and have the index allocation set to put indices that need SSDs on one set of machines, and the ones with disk on the others. On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > Also, open an issue? > > On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > No, its not possible, though it makes sense. Shouldn't be too difficult > > to add, just requires thinking on how to expose it. > > > > On Wed, Jun 13, 2012 at 11:23 AM, Niklas Therning [niklas@therning.org](mailto:niklas@therning.org)wrote: > > > > > Hi, > > > > > > Is it possible to set path.data per index? We would like to store one > > > index on a dedicated SSD while other indexes will be stored on slower HDDs. > > > > > > /Niklas ---
**Author:** ![Niklas\_Therning](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/niklas_therning/32/2847_2.png) [@Niklas\_Therning](https://discuss.elastic.co/u/Niklas_Therning)\ **Post date:** [June 15, 2012, 8:18am UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075/5 "2012-06-15T08:18:52Z")
Issue created here: > > > It would be great to be able to store data files for different indices in differ…ent paths. My use case is that I have servers with both fast SSDs and slow HDDs. I'd like to have one of my indices stored on the SSD while the others would be stored on the HDD. > > It would also be cool if this setting could be changed at runtime. Then I could move a "hot" index to the SSD and swap out less hotter ones using cron. We use rolling indices based on date and the two most recent ones are the targets of almost all search/index requests. I just discovered the shard allocation stuff and will look into how we can use it. Thanks! /Niklas On 2012-06-14 23:27, Shay Banon wrote: > One more thing, you can have SSDs on some machines, and disks on > others, and have the index allocation set to put indices that need > SSDs on one set of machines, and the ones with disk on the others. > > On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon \<[kimchy@gmail.com](mailto:kimchy@gmail.com) > [mailto:kimchy@gmail.com](mailto:kimchy@gmail.com)\> wrote: > > ``` > Also, open an issue? > > On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon > wrote: > > No, its not possible, though it makes sense. Shouldn't be too > difficult to add, just requires thinking on how to expose it. > > On Wed, Jun 13, 2012 at 11:23 AM, Niklas Therning > > wrote: > > Hi, > > Is it possible to set path.data per index? We would like > to store one index on a dedicated SSD while other indexes > will be stored on slower HDDs. > > /Niklas > > ``` ---
**Author:** ![Kavin\_Xavier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kavin_xavier/32/2590_2.png) [@Kavin\_Xavier](https://discuss.elastic.co/u/Kavin_Xavier)\ **Post date:** [June 15, 2012, 11:06am UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075/6 "2012-06-15T11:06:20Z")
This would become a very nice feature. One more thing I should add to this is the ability to move an existing index from SSD to a HDD when we feel that the current index is no longer the most searched index. For example, News articles, our application indexes hundreds of millions of news articles and we create index per day. Everyday, the index would become 20 GB in size. Wr would like to have the first 10 days' index in SSD and the others in HDDs so that the search will be pretty fast in the default stories section and then move the last days index to HDD when we create a new index. So, basically, if there is a mechanism to move an index from SSD to HDD, that would be very helpful. Not a reasonable request? Regards, Kavin On Fri, Jun 15, 2012 at 1:48 PM, Niklas Therning [niklas@therning.org](mailto:niklas@therning.org)wrote: > Issue created here: > [Add per index path.data setting · Issue #2025 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2025) > > I just discovered the shard allocation stuff and will look into how we can > use it. Thanks! > > /Niklas > > On 2012-06-14 23:27, Shay Banon wrote: > > One more thing, you can have SSDs on some machines, and disks on others, > and have the index allocation set to put indices that need SSDs on one set > of machines, and the ones with disk on the others. > > On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > Also, open an issue? > > > > On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > > > No, its not possible, though it makes sense. Shouldn't be too difficult > > > to add, just requires thinking on how to expose it. > > > > > > On Wed, Jun 13, 2012 at 11:23 AM, Niklas Therning [niklas@therning.org](mailto:niklas@therning.org)wrote: > > > > > > > Hi, > > > > > > > > Is it possible to set path.data per index? We would like to store one > > > > index on a dedicated SSD while other indexes will be stored on slower HDDs. > > > > > > > > /Niklas ---
**Author:** ![Kavin\_Xavier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kavin_xavier/32/2590_2.png) [@Kavin\_Xavier](https://discuss.elastic.co/u/Kavin_Xavier)\ **Post date:** [June 15, 2012, 11:08am UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075/7 "2012-06-15T11:08:05Z")
Oops, sorry I think Niklas already added this to his request. Good one. Thanks! Kavin On Fri, Jun 15, 2012 at 4:36 PM, Kavin Xavier [kavin.db@gmail.com](mailto:kavin.db@gmail.com) wrote: > This would become a very nice feature. One more thing I should add to this > is the ability to move an existing index from SSD to a HDD when we feel > that the current index is no longer the most searched index. For example, > News articles, our application indexes hundreds of millions of news > articles and we create index per day. Everyday, the index would become 20 > GB in size. Wr would like to have the first 10 days' index in SSD and the > others in HDDs so that the search will be pretty fast in the default > stories section and then move the last days index to HDD when we create a > new index. So, basically, if there is a mechanism to move an index from SSD > to HDD, that would be very helpful. Not a reasonable request? > > Regards, > Kavin > > On Fri, Jun 15, 2012 at 1:48 PM, Niklas Therning [niklas@therning.org](mailto:niklas@therning.org)wrote: > > > Issue created here: > > [Add per index path.data setting · Issue #2025 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/issues/2025) > > > > I just discovered the shard allocation stuff and will look into how we > > can use it. Thanks! > > > > /Niklas > > > > On 2012-06-14 23:27, Shay Banon wrote: > > > > One more thing, you can have SSDs on some machines, and disks on others, > > and have the index allocation set to put indices that need SSDs on one set > > of machines, and the ones with disk on the others. > > > > On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > > > Also, open an issue? > > > > > > On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > > > > > > No, its not possible, though it makes sense. Shouldn't be too difficult > > > > to add, just requires thinking on how to expose it. > > > > > > > > On Wed, Jun 13, 2012 at 11:23 AM, Niklas Therning [niklas@therning.org](mailto:niklas@therning.org)wrote: > > > > > > > > > Hi, > > > > > > > > > > Is it possible to set path.data per index? We would like to store one > > > > > index on a dedicated SSD while other indexes will be stored on slower HDDs. > > > > > > > > > > /Niklas ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:23am UTC](https://discuss.elastic.co/t/per-index-path-data-setting-possible/8075/8 "2017-07-06T03:23:55Z")