Thank you Hoss, this is exactly what I need! Currently I perform reindexing once a month, and it takes few days... Very slow... Over 2 millions documents (not too much; 300Mb in files), database & SOLR on a same box, and SOLR uses about 60-80% CPU. I will implement real-time updates, via direct Java calls (as soon as data gets changed).
About Compass, I noticed some messages. I tried to use it (before SOLR) because of advertised "transactional" Lucene updates; that is not true, and performance was really bad. -----Original Message----- From: Chris Hostetter postCommit and postOptimize hooks can be subclass of SolrEventListener so you can trigger arbitrary jva code if you want to write your own (use JMS, or make an HTTP call, whatever) the RunExecutableListener that ships with Solr would be the easiest thing to do ... just have it execute the "commit" command line script on your slave (which will make it reopen the index you just modified)
