Configuring refresh_interval at the query level


(nariman) #1

We've had some success improving bulk insertion times using a higher value
for refresh_interval when doing bulk inserts.

However, the global nature of this setting seems to cause some problems.

We want some insertions processed with a higher value and others processed
immediately (under the default 1s).... there's no way to safely do this in
a concurrent environment where end-user actions are triggering index
updates.

Any suggestions on how to handle this?

--
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/2b6d9820-874c-4b10-91d3-3493fe8efd17%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(Jörg Prante) #2

refresh_interval does not control insertions doc by doc, it works on index
level, telling a shard it has to switch from written buffer to a readable
(searchable) index, which can be a heavy operation related to hundreds and
thousands of words in your documents.

You can index into two different indexes, one with refresh disabled, one
with refresh enabled.

Jörg

--
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/CAKdsXoEboQW95yocQKOHONOaj%2BBX%2B6a-AViYC8W%2Ba6TxOuw9%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #3