I don't know anything about LifeRay (never heard of it), but it sounds like 
you've actually figured out what you need to know about LifeRay, all you've got 
left is: "how to replicate the writer solr server content into the readers."

This should tell you how: 
http://wiki.apache.org/solr/SolrReplication

You'll need to find and edit the configuration files for the Solr's involved -- 
if you don't normally do that because LifeRay hides em from you, you'll need to 
find em. But it's a straightforward Solr feature (since 1.4), replication. 
________________________________________
From: Roman, Pablo [pablo.ro...@uhn.ca]
Sent: Thursday, August 11, 2011 12:10 PM
To: solr-user@lucene.apache.org
Subject: need some guidance about how to configure a specific solr solution.

Hi There,

I am IT and  work on a project based on Liferary 605 with solr-3.2 like the 
indexer/search engine.

I presently have only one server that is indexing and searching but reading the 
Liferay Support suggestions they point to the need of having:
- 2 to n SOLR read-server for searching from any member of the liferay cluster
- 1 SOLR write-server where all liferay cluster members write.

However, going down to detail to implement that on the liferay side I think I 
know how to do that which is inserting into the plugin for Solr this entries

 solr-spring.xml in the WEB-INF/classes/META-INF folder. Open this file in a 
text editor and you will see that there are two entries which define where the 
Solr server can be found by Liferay:

<bean id="indexSearcher" 
class="com.liferay.portal.search.solr.SolrIndexSearcherImpl"> <property 
name="serverURL" value="http://localhost:8080/solr/select"; /> </bean> <bean 
id="indexWriter" class="com.liferay.portal.search.solr.SolrIndexWriterImpl"> 
<property name="serverURL" value="http://localhost:8080/solr/update"; /> </bean>

However, I don't know how to replicate the writer solr server content into the 
readers. Please can you provide advice about that?

Thanks,
Pablo

This e-mail may contain confidential and/or privileged information for the sole 
use of the intended recipient.
Any review or distribution by anyone other than the person for whom it was 
originally intended is strictly prohibited.
If you have received this e-mail in error, please contact the sender and delete 
all copies.
Opinions, conclusions or other information contained in this e-mail may not be 
that of the organization.

Reply via email to