Curator and disable shard allocation


(Klaus Kleber) #1

Hey Guys,

We have set up a ES-cluster on a very powerful machine, where 1 node have
the SSD assigned and the other nodes the slow HDD´s.

We want to reallocate the indices after 7 days to the HDD´s which is very
easy using the curator-tool.

Logstash is configured to send the indexed events to port 9200 on which the
SSD-ES-Node is listen too.

But we elasticsearch rebalances the index between the SSD and the HDD node,
making the performance advantage of the SSD useless.

So i´ve search and found the cluster.routing.allocation.enable:none parameter
for elasticsearch.

I´ve I now disable routing allocation for the indexes, will curator still
work?

Thanks

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ec7ecac0-d524-404b-aad9-5048f6cc61a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Mark Walkom) #2

You don't want that, take a look at

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: markw@campaignmonitor.com
web: www.campaignmonitor.com

On 25 August 2014 17:38, Klaus Kleber brianmoser23@gmail.com wrote:

Hey Guys,

We have set up a ES-cluster on a very powerful machine, where 1 node have
the SSD assigned and the other nodes the slow HDD´s.

We want to reallocate the indices after 7 days to the HDD´s which is very
easy using the curator-tool.

Logstash is configured to send the indexed events to port 9200 on which
the SSD-ES-Node is listen too.

But we elasticsearch rebalances the index between the SSD and the HDD
node, making the performance advantage of the SSD useless.

So i´ve search and found the cluster.routing.allocation.enable:none parameter
for elasticsearch.

I´ve I now disable routing allocation for the indexes, will curator still
work?

Thanks

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/ec7ecac0-d524-404b-aad9-5048f6cc61a4%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/ec7ecac0-d524-404b-aad9-5048f6cc61a4%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624YbThF52u_GGtUscKh_c2r49Hsb6kwU9q%2BMnSaZmt4qyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(Klaus Kleber) #3

Hi,

yes i found that article but as soon as i start the HDD-node, elasticsearch
starts to reallocate shards to it and thus if you search sth. in Kibana it
will also searched from the slow HDD´s which we want to avoid.

We want that the whole index lies on the SSD until we reallocate it using
curator

Am Montag, 25. August 2014 09:42:16 UTC+2 schrieb Mark Walkom:

You don't want that, take a look at
https://github.com/elasticsearch/curator/wiki/Routing-Allocation

Regards,
Mark Walkom

Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com <javascript:>
web: www.campaignmonitor.com

On 25 August 2014 17:38, Klaus Kleber <brianm...@gmail.com <javascript:>>
wrote:

Hey Guys,

We have set up a ES-cluster on a very powerful machine, where 1 node have
the SSD assigned and the other nodes the slow HDD´s.

We want to reallocate the indices after 7 days to the HDD´s which is very
easy using the curator-tool.

Logstash is configured to send the indexed events to port 9200 on which
the SSD-ES-Node is listen too.

But we elasticsearch rebalances the index between the SSD and the HDD
node, making the performance advantage of the SSD useless.

So i´ve search and found the cluster.routing.allocation.enable:none parameter
for elasticsearch.

I´ve I now disable routing allocation for the indexes, will curator still
work?

Thanks

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/ec7ecac0-d524-404b-aad9-5048f6cc61a4%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/ec7ecac0-d524-404b-aad9-5048f6cc61a4%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/364d5bfe-c00e-4a49-b682-34f03ead0bea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(system) #4