One of our indices has a fairly high document count (around 100 million)
and a high update and delete rate. In any given day, maybe a quarter of
those documents will be updated, replaced, or deleted. Given this, the
default merge settings don't seem to be keeping up and the percentage of
deleted documents slowly creeps up. A lot of these documents are child
documents so this seems to also increase memory pressure as the parent ID
cache is growing along with the delete count. It only seems to clear when a
whole segment is deleted.
I've looked in to the merge and store settings and I'm wondering what the
best course of action to address this is? So far I've increased the
reclaim_delete_weight from 2.0 to 3.0 and changed max_merge_at_once and
segments_per_tier to 5. Store throttle is still enabled, but is set to
80mb/s and the hardware should be capable of at least that. I'm not
completely sure that's the right direction as they don't really seem to
have made any difference. Increasing the throttle rate doesn't seem to have
reduced the store throttle time metric, and the deleted document ratio is
Anyone else had any experience with this sort of indexing load? In case
I've made a typo somewhere, our actual settings look like 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 email@example.com.
For more options, visit https://groups.google.com/groups/opt_out.