: Thats the thing,Terracotta persists everything it has in memory to the : disk when it overflows(u can set how much u want to use in memory), or : when the server goes offline. When the server comes back the master : terracotta simply loads it back into the memory of the once offline
Sure .. but Terracotta needs some control over the RAMDirectory to do all this ... i'm also assuming that for the "loading back into memory" part to work when a server starts up, terracotta actually needs to *own* the RAMDirectory, so just making solr create a RAMDirectory on startup based on a config option wouldn't be enough ... there would need to be some (probably complex) hooks to determine how that RAMDirectory gets created/managed to make what you are describing work. -Hoss
