I am trying to minimize the indexes replication latency (in JMS master/slave the default refresh interval is half hour as described at ).
I have found interesting articles  and :
"Latency: the slave nodes need refreshing their local index folders after a fixed period. So there is a latency between master and slave to see a newly indexed item" 
"To that end, HIbernate Search doesn't rely on JBossCache or any in-memory partitioning / caching schemes and instead relies on JMS and each JVM's local disk in order to provide up-to-date indexing across a cluster with simultaneous low latency" 
It's seems that solution described at  can provide up to date indexes with low latency by replaying the lucene actions on each local lucene index using JMS topic. What do you think about this solution?
 http://docs.jboss.org/hibernate/stable/ ... ms-backend
 http://linhtech.wordpress.com/2010/10/0 ... mentation/
 http://stackoverflow.com/questions/8858 ... ate-search