Set higher index.priority for high ingest throughput indices?

Hey,

Does anyone know if it makes sense to set a higher index.priority value for indices which have a high ingest throughput?

My thinking is that during a rolling restart or just some node maintenance, we don't want to recover the low throughput indices first because whilst that is happening, the amount of data that will need to be copied for the high throughput indices is growing very quickly.

Therefore, if we recover the high throughput indices first, it means we limit the amount of data that needs to be copied to the node once it's back up, which should allow recovery to complete faster. Or is that nonsense?

Thanks!

For anyone interested in this, I tested it on our clusters and I didn't see any impact.

Thanks for reaching out, @tronboto. It seems you found a solution, but I wanted to check in to see if there was anything else you needed.