I have a SolrCloud v5.4 collection with 3 replicas that appear to have fallen
permanently out of sync. Users started to complain that the same search,
executed twice, sometimes returned different result counts. Sure enough, our
replicas are not identical:
>> shard1_replica1: 89867 documents
check
>itself.
>
>You might watch the achieved replication factor of your updates and see if it
>ever changes:
>https://cwiki.apache.org/confluence/display/solr/Read+and+Write+Side+Fault+Tolerance
> (See Achieved Replication Factor/min_rf)
>
>If it does, that might give you
orks/
>
>So the fact that you encountered this sounds like a bug to me.
>That said, another general recommendation (of mine) is that you not use Solr
>as your primary data source, so you can rebuild your index from scratch if you
>really need to.
>
>
>
>
>
>
>On 1/26
date some of Solr’s assumptions.
>
>
>
>
>On 1/27/16, 7:59 AM, "David Smith" wrote:
>
>>Jeff, again, very much appreciate your feedback.
>>
>>It is interesting — the article you linked to by Shalin is exactly why we
>>picked SolrCloud over ES, beca
On 1/28/16, 1:08 PM, "Tomás Fernández Löbbe" wrote:
>Maybe you are hitting the reordering issue described in SOLR-8129?
>
>Tomás
>
>On Wed, Jan 27, 2016 at 11:32 AM, David Smith
>wrote:
>
>> Sure. Here is our SolrCloud cluster:
>>
>>+ T
Erick,
So that my understanding is correct, let me ask, if one or more replicas are
down, updates presented to the leader still succeed, right? If so, tedsolr is
correct that the Solr client app needs to re-issue updates, if it wants
stronger guarantees on replica consistency than what Solr pr
I am trying to use “languid.map.individual” setting to allow field “a” to
detect as, say, English, and be mapped to “a_en”, while in the same document,
field “b” detects as, say, German and is mapped to “b_de”.
What happens in my tests is that the global language is detected (for example,
Germa
I have a prototype SolrCloud 4.10.2 setup with 13 collections (of 1 replica, 1
shard each) and a separate 1-node Zookeeper 3.4.6.
The very first app test case I wrote is failing intermittently in this
environment, when I only have 4 documents ingested into the cloud.
I dug in and found when I q
ember 16, 2014 12:01 PM, Alexandre Rafalovitch
wrote:
Facet counts include deleted documents until the segments merge. Could that
be an issue?
Regards,
Alex
On 16/12/2014 12:18 pm, "David Smith" wrote:
> I have a prototype SolrCloud 4.10.2 setup with 13 collections (of 1
t happen and try again (very low probability that this is the
root cause, but you never know).
but it sure sounds like one replica doesn't agree with another, so the
above will give us place to look.
Best,
Erick
On Tue, Dec 16, 2014 at 12:12 PM, David Smith
wrote:
> Alex,
> Good sug
uent cores.
workarround is to set mincount=0 for your facet ranges.
: Date: Tue, 16 Dec 2014 17:17:05 + (UTC)
: From: David Smith
: Reply-To: solr-user@lucene.apache.org, David Smith
: To: Solr-user
: Subject: Identical query returning different aggregate results
:
: I have a prototype
I have a query against a single 50M doc index (175GB) using Solr 4.10.2, that
exhibits the following response times (via the debugQuery option in Solr Admin):
"process": {
"time": 24709,
"query": { "time": 54 }, "facet": { "time": 24574 },
The query time of 54ms is great and exactly as expecte
Shawn,
Thanks for the suggestion, but experimentally, in my case the same query with
facet.method=enum returns in almost the same amount of time.
Regards
David
On Tuesday, January 13, 2015 12:02 PM, Shawn Heisey
wrote:
On 1/13/2015 10:35 AM, David Smith wrote:
> I have a qu
ilters. The API is different, you'll have to provide the intervals
yourself.
Tomás
On Tue, Jan 13, 2015 at 10:01 AM, Shawn Heisey wrote:
> On 1/13/2015 10:35 AM, David Smith wrote:
> > I have a query against a single 50M doc index (175GB) using Solr 4.10.2,
> that exhibits th
should create a Jira to add
this feature to interval faceting.
Tomás
On Tue, Jan 13, 2015 at 10:44 AM, David Smith
wrote:
> Tomás,
>
>
> Thanks for the response -- the performance of my query makes perfect sense
> in light of your information.
> I looked at Interval faceting.
Shawn,
I've been thinking along your lines, and continued to run tests through the
day. The results surprised me.
For my index, Solr range faceting time is most closely related to the total
number of documents in the index for the range specified. The number of
"buckets" in the range is a sec
16 matches
Mail list logo
