ing strategy back to composite (which it should be). is
> it ok? Do I need to do anything more than simply changing the strategy in
> the clusterState.json?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4325001.html
> Sent from the Solr - User mailing list archive at Nabble.com.
?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4325001.html
Sent from the Solr - User mailing list archive at Nabble.com.
omething went wrong and
> `implicit` router got created.
>
> Can I simply change the `clusterstate.json` to take care of this?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p432
and
`implicit` router got created.
Can I simply change the `clusterstate.json` to take care of this?
--
View this message in context:
http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4324950.html
Sent from the Solr - User mailing list archive
t and duplicate records (random records) in shards.
>
> Also, This started happening after 1 of our zookeeper died due to hardware
> issue and we had to setup a new zookeeper machine. update the config in all
> the solr machine and restart the cloud.
>
>
>
>
>
> --
context:
http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4324937.html
Sent from the Solr - User mailing list archive at Nabble.com.
On 3/13/2017 3:16 AM, vbindal wrote:
> I am facing the same issue where my query *:* returns inconsistent number
> (almost 3) time the actual number in millions.
>
> When I try disturb=false on every machine, the results are correct. but
> without `disturb=false` results are incorrect.
This most
message in context:
http://lucene.472066.n3.nabble.com/Inconsistent-numFound-in-SC-when-querying-core-directly-tp4105009p4324561.html
Sent from the Solr - User mailing list archive at Nabble.com.
I spoke too soon, my plan for fixing this didn't quite work.
I've moved this issue into a new thread/topic: "No /clusterstate.json
updates on Solrcloud 4.3.1 Cores API UNLOAD/CREATE".
Thanks all for the help on this one!
Tim
On 5 December 2013 11:37, Tim Vaillancourt wrote:
> Very good point
Very good point. I've seen this issue occur once before when I was playing
with 4.3.1 and don't remember it happening since 4.5.0+, so that is good
news - we are just behind.
For anyone that is curious, on my earlier mention that
Zookeeper/clusterstate.json was not taking updates: this was NOT co
Keep in mind, there have been a *lot* of bug fixes since 4.3.1.
- Mark
On Dec 4, 2013, at 7:07 PM, Tim Vaillancourt wrote:
> Hey all,
>
> Now that I am getting correct results with "distrib=false", I've identified
> that 1 of my nodes has just 1/3rd of the total data set and totally explains
Hey all,
Now that I am getting correct results with "distrib=false", I've
identified that 1 of my nodes has just 1/3rd of the total data set and
totally explains the flapping in results. The fix for this is obvious
(rebuild replica) but the cause is less obvious.
There is definately more tha
Chris, this is extremely helpful and it's silly I didn't think of this
sooner! Thanks a lot, this makes the situation make much more sense.
I will gather some proper data with your suggestion and get back to the
thread shortly.
Thanks!!
Tim
On 04/12/13 02:57 PM, Chris Hostetter wrote:
:
:
:
: I may be incorrect here, but I assumed when querying a single core of a
: SolrCloud collection, the SolrCloud routing is bypassed and I am talking
: directly to a plain/non-SolrCloud core.
No ... every query received from a client by solr is handled by a single
core -- if that core knows it'
.org
Subject: Re: Inconsistent numFound in SC when querying core directly
To add two more pieces of data:
1) This occurs with real, conditional queries as well (eg:
"q=key:timvaillancourt"), not just the "q=*:*" I provided in my email.
2) I've noticed when I bring a node of t
atest commits now (since tuesday) and are still waiting for it to
happen again.
-Original message-
> From:Tim Vaillancourt
> Sent: Wednesday 4th December 2013 23:38
> To: solr-user@lucene.apache.org
> Subject: Re: Inconsistent numFound in SC when querying core directly
>
To add two more pieces of data:
1) This occurs with real, conditional queries as well (eg:
"q=key:timvaillancourt"), not just the "q=*:*" I provided in my email.
2) I've noticed when I bring a node of the SolrCloud down it is
remaining "state: active" in my /clusterstate.json - something is rea
Hey guys,
I'm looking into a strange issue on an unhealthy 4.3.1 SolrCloud with
3-node external Zookeeper and 1 collection (2 shards, 2 replicas).
Currently we are noticing inconsistent results from the SolrCloud when
performing the same simple /select query many times to our collection.
Alm
18 matches
Mail list logo
