Hi, I'm building an application that dynamically instantiates a large number of solr cores on a single machine (large would ideally be as high as I can get it, in the millions, if it is possible to do so without significant performance degradation and/or system failure). I already tried this same use case as a single-core index and found that as my index grew large, performance became devastatingly slow, which I have so far not seen in the multicore setup.
What I have seen, however, is that the number of open FDs steadily increases with the number of cores opened and files indexed, until I hit whatever upper bound happens to be set (currently 100k). Raising machine-imposed limits, using the compound file format, etc are only holdovers. I was thinking it would be nice if I could keep some kind of MRU cache of cores such that Solr only keeps open resources for the cores in the cache, but I'm not sure if this is allowed. I saw that SolrCore has a close() function, but if my understanding is correct, that isn't exposed to the client. Would anyone know if there are any ways to de/reallocate resources for different cores at runtime? Thanks, Dan -- View this message in context: http://www.nabble.com/Question-About-Solr-Cores-tp24432008p24432008.html Sent from the Solr - User mailing list archive at Nabble.com.
