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 worker..identical to the approach SOLR already does to handle scalability...., this allows unlimited storage of the items in memory, ... you just need to cluster the "RAMDirectory" according to the sample giving by Terracotta....However i read some of the post here...I read some say: " i wonder how performance will be".,etc....i was trying to get it working..andload test the hell out it, and see how it acts with large amounts of data, and how it ompares with SOLR using typical FSDirectory approach.i plan to post findings..Jeryl Cook
/^\ Pharaoh /^\ http://pharaohofkush.blogspot.com/ "..Act your age, and not your shoe size.." -Prince(1986)> Date: Thu, 31 May 2007 13:51:53 -0700> From: [EMAIL PROTECTED]> To: solr-user@lucene.apache.org> Subject: RE: RAMDirecotory instead of FSDirectory for SOLR> > > : board, looks like i can achieve this with the "embedded" version of SOLR> : uses the lucene RAMDirectory to store the index..Jeryl Cook> > yeah ... adding asolrconfig.xml option for using a RAMDirectory would be> possible ... but almost meaningless for most people (the directory would> go away when the server shuts down) ... even for use cases like what you> describe (hooking in terrecota) it wouldn't be enough in itself, because> there would be no hook to give terracota access to it.> > > -Hoss>
