Per index path.data setting possible?

Elastic Stack Elasticsearch
1

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

2

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.orgwrote:

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

3

Also, open an issue?

On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon 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.orgwrote:

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

4

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 wrote:

Also, open an issue?

On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon 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.orgwrote:

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

5

Issue created here:

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
6

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.orgwrote:

Issue created here:
Add per index path.data setting · Issue #2025 · elastic/elasticsearch · GitHub

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 wrote:

Also, open an issue?

On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon 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.orgwrote:

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

7

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 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.orgwrote:

Issue created here:
Add per index path.data setting · Issue #2025 · elastic/elasticsearch · GitHub

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 wrote:

Also, open an issue?

On Thu, Jun 14, 2012 at 11:09 PM, Shay Banon 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.orgwrote:

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