Hi,
I Installed 3 instances of SolrCloud 5.4.1.
I'm doing a little search engine of websites and I'm store their info as
Nested Documents(one document for the website general information and it
children is the pages inside the website).
So when I'm querying this collection I'm using a BlockJoin par
On Jun 10, 2011, at 12:26 AM, Upayavira wrote:
> I'm exploring SolrCloud for a new project, and have some questions based
> upon what I've found so far.
>
> The setup I'm planning is going to have a number of multicore hosts,
> with cores being moved between hosts, and potentially with cores mer
All of Solr is still under development ;)
If you do a bit of searching, you might find slides/video of a talk about how
http://www.loggly.com/ has been using SolrCloud in production for some time
now. They have been pretty happy with it based on what they have said.
Still need to tackle the in
Mohammad,
There are two sides to using SolrCloud in production - the SolrCloud
code, and the Solr 4.0 code that it is a part of.
You can reduce the risk of being caught out by Solr/Lucene 4.0 changes
(e.g. index structure changes) by using a Lucene 3.0 index format within
Solr 4.0. While there's
I am also planning to move to SolrCloud;
since its still in under development, I am not sure about its behavior in
Production.
Please update us once you find it stable.
On 10 June 2011 03:56, Upayavira wrote:
> I'm exploring SolrCloud for a new project, and have some questions based
> upon what
I'm exploring SolrCloud for a new project, and have some questions based
upon what I've found so far.
The setup I'm planning is going to have a number of multicore hosts,
with cores being moved between hosts, and potentially with cores merging
as they get older (cores are time based, so once today
at the possibility to specify alternative shards
>> if one is not available)? If it does not know that they are replicas of
>> eachother, I should use the syntax of specifying alternative shards for
>> failover due to performance-reasons, because querying 2 identical and
>> avai
the syntax of specifying alternative shards for
> failover due to performance-reasons, because querying 2 identical and
> available cores seems to be wasted capacity, no?
>
> Thank you!
>
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-Questions-for
failover due to performance-reasons, because querying 2
>> identical and available cores seems to be wasted capacity, no?
>>
>> Thank you!
>>
>
>
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-Questions-for-MultiCore-Setup-tp2309443p2327089.html
Sent from the Solr - User mailing list archive at Nabble.com.
at they are replicas of
> eachother, I should use the syntax of specifying alternative shards for
> failover due to performance-reasons, because querying 2 identical and
> available cores seems to be wasted capacity, no?
>
> Thank you!
>
--
View this message in context:
htt
ntext:
http://lucene.472066.n3.nabble.com/SolrCloud-Questions-for-MultiCore-Setup-tp2309443p2312763.html
Sent from the Solr - User mailing list archive at Nabble.com.
llection2
> SWAP core1,core2
> Does core2 now maps to collection1?
>
> Thank you!
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/SolrCloud-Questions-for-MultiCore-Setup-tp2309443p2309443.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
--
Lance Norskog
goks...@gmail.com
u!
--
View this message in context:
http://lucene.472066.n3.nabble.com/SolrCloud-Questions-for-MultiCore-Setup-tp2309443p2309443.html
Sent from the Solr - User mailing list archive at Nabble.com.
13 matches
Mail list logo
