The slaves will be able to replicate from the master as before but not
in NRT depending on your commit interval. Commit interval can be set
higher for NRT as it is not needed for searches except for consolidating
the index changes on the master and can be an hr or even more. It maybe
easier to update the slaves directly as the update/query performance is
high (replication in the cloud in 4.0 also follows similar paradigm as
the docs are sent across as a whole to be replicated. So for now you may
have to do this manually)
- Nagendra Nagarajayya
http://solr-ra.tgels.org
http://rankingalgorithm.tgels.org
On 2/15/2012 8:35 AM, Dipti Srivastava wrote:
Hi Nagendra,
Certainly interesting! Would this work in a Master/slave setup where the
reads are from the slaves and all writes are to the master?
Regards,
Dipti Srivastava
On 2/15/12 5:40 AM, "Nagendra Nagarajayya"<nnagaraja...@transaxtions.com>
wrote:
If you are looking for NRT functionality with Solr 3.5, you may want to
take a look at Solr 3.5 with RankingAlgorithm. This allows you to
add/update documents without a commit while being able to search
concurrently. The add/update performance to add 1m docs is about 5000
docs in about 498 ms with one concurrent searcher. You can get more
information about Solr 3.5 with RankingAlgorithm from here:
http://tgels.org/wiki/en/Near_Real_Time_Search_ver_3.x
Regards,
- Nagendra Nagarajayya
http://solr-ra.tgels.org
http://rankingalgorithm.tgels.org
On 2/14/2012 4:41 PM, Dipti Srivastava wrote:
Hi All,
Is there a way to soft commit in the current released version of solr
3.5?
Regards,
Dipti Srivastava
This message is private and confidential. If you have received it in
error, please notify the sender and remove it from your system.
This message is private and confidential. If you have received it in error,
please notify the sender and remove it from your system.
