0 Replies Latest reply on Mar 18, 2013 10:09 AM by grigor.tonkov

    Lucene in Master / Slave Mode - Slave writes to index too

    grigor.tonkov

      Hello Sane,

      we use HSearch with Lucene in the Master/Slave configuration as described here (not JMS but using JGroups).

      http://docs.jboss.org/hibernate/search/3.2/reference/en/html/search-configuration.html#jgroups-backend

       

       

      We have the following configuration: (finaly found one mix working properly :-( )

       

          <hibernate-version>3.6.8.Final</hibernate-version>

          <hibernate-search-version>3.4.2.Final</hibernate-search-version>

          <lucene-version>3.6.1</lucene-version>

          <infinispan-version>4.2.0.FINAL</infinispan-version><!-- WARNING: only 4.2.0.FINAl has the locks properly implemented , but not 4.2.1  -->

          <drools-version>4.0.7</drools-version>

          <janino-version>2.5.10</janino-version>

          <!-- for drools 4.0.7 -->

          <jboss-version>6.1.0.Final</jboss-version>

       

       

      My questions are:

       

      1. Is it possible to configre the lucene indexing in way so that the Slave is writing to its index (or additional index) so that the slave has its updates without waitng the master to send update via JMS or JGroups.

      2. What could be the problem using NFS as sharing mechanism for the master? Is it possible locking ? Will it be a problem with the master shared index is down and not available ?

       

      Thank you in advance!

      Grigor