why should i use Solandra instead of NRT only with Solr and own
configurations !?
-
--- System
One Server, 12 GB RAM, 2 Solr Instances, 7 Cores,
1 Core with 31 Million Documents other Cores < 100.000
- Solr1 for Search-Re
Peter,
thanks for sharing.
It sounds interesting. However: What are the downsides of this combo?
Regards
Peter Karich wrote:
>
> First, its more Solandra now (although the project is still named
> lucandra) ;)
>
> Second, it can help because data which is written to the index is
> immediate
First, its more Solandra now (although the project is still named
lucandra) ;)
Second, it can help because data which is written to the index is
immediately (configurable) available for search.
solandra is distributed + real time solr, with no changes required on
client side (be it SolrJ or othe
Out of curiousity, how would Lucandra help in the NRT use case?
On Thu, Jan 20, 2011 at 11:42 PM, Espen Amble Kolstad wrote:
> I haven't tried myself, but you could look at solandra :
> https://github.com/tjake/Lucandra
>
> - Espen
>
> On Thu, Jan 20, 2011 at 6:30 PM, stockii wrote:
>>
>> http:/
I haven't tried myself, but you could look at solandra :
https://github.com/tjake/Lucandra
- Espen
On Thu, Jan 20, 2011 at 6:30 PM, stockii wrote:
>
> http://wiki.apache.org/solr/NearRealtimeSearchTuning
>
> http://lucene.472066.n3.nabble.com/Tuning-Solr-caches-with-high-commit-rates-NRT-td14612
http://wiki.apache.org/solr/NearRealtimeSearchTuning
http://lucene.472066.n3.nabble.com/Tuning-Solr-caches-with-high-commit-rates-NRT-td1461275.html
http://lucene.472066.n3.nabble.com/NRT-td2276967.html#a2278477
-
--- System
