Hi Joerg & Itamar,
Thanks for your reply. What I am trying to get is an order of magnitue.
Suppose a server has 20GB RAM. Each index has about 20K documents, each
document is about 500 words, average term distribution. The question is
whether the server would be able to smoothly handle tenths, hundreds, or
thousands (or more?) of open indices. Suppose each index gets about 10 new
documents per minute, and serves about 30 queries per minute.
בתאריך יום שני, 3 במרץ 2014 19:04:22 UTC+2, מאת Jörg Prante:
Sure, you can create hundreds of thousands of indices, without docs, or
with just one doc. Closing an index even frees the resources of the index
management. This is not useful, just an edge case.
I'm afraid this is not the answer to the question.
The number of open indices (shards) is limited by disk space and maximum
number of file descriptors. But that is also theoretical. Using all indices
at once will use more resources than file descriptors. It depends on the
index / query characteristics (RAM for shards, fields, term count, term
distribution etc.) That is not directly related to "powerful" servers. Even
the weakest server can create as much indices as the strongest one.
Putting workload on indices is a different story.
Joerg, I think what Adam means is how many open indexes an ES instance
can hold before lagging or crashing (assuming max open files is set
Small indexes usually mean less segments per index, so the question may
boil down mostly to number of open IR/IW?
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/46fb6eed-ef7d-4fb1-93e7-020b0218c063%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.