RE: Delayed/waiting requests

Hi Erick, Thank you for your detailed answer, I better understand autowarming. We have an autowarming time of ~10s for filterCache (queryResultCache is not used at all, ratio = 0.02). We increased the size of the filterCache from 6k to 12k (and autowarming size set to same values) to have a

join query and new searcher on joined collection

Solr 6.3 I have a query like this: q=*:*{!join score=none from=id fromIndex=hss_4 to=rpk_hdquotes v=$qq}*:* -- Vadim

RE: join query and new searcher on joined collection

Sory, I've sent unfinished message So, query on collection1 q=*:*{!join score=none from=id fromIndex=collection2 to=field1}*:* The question is what happened with autowarming and new searchers on collection1 when new searcher starts on collection2? IMHO when request with join comes it's impossible

Re: "no servers hosting shard" when querying during shard creation

On 13/01/2019 19:43, Erick Erickson wrote: > Yeah, that seems wrong, I'd say open a JIRA. I've created a bug in Jira: SOLR-13136. Should I assign this to anyone? Unsure what the procedure is there. Incidentally, while doing so I noticed that 7.6 is still "unreleased" according to Jira. Thanks,

Re: DateRangeField requires month?

I did some testing by tweaking DateRangeFieldTest and witness that 2000-11T13 is parsed as 2000-11-13 see https://github.com/apache/lucene-solr/blob/f083473b891e596def2877b5429fcfa6db175464/lucene/spatial-extras/src/java/org/apache/lucene/spatial/prefix/tree/DateRangePrefixTree.java#L462 Don't know

Re: DateRangeField requires month?

Follow up https://issues.apache.org/jira/browse/SOLR-13139 On Tue, Jan 15, 2019 at 2:46 PM Mikhail Khludnev wrote: > I did some testing by tweaking DateRangeFieldTest and witness that > 2000-11T13 is parsed as 2000-11-13 see > > https://github.com/apache/lucene-solr/blob/f083473b891e596def2877b5

Re: join query and new searcher on joined collection

collection1 has no idea about new searcher in collection2. On Tue, Jan 15, 2019 at 1:18 PM Vadim Ivanov < vadim.iva...@spb.ntk-intourist.ru> wrote: > Sory, I've sent unfinished message > So, query on collection1 > q=*:*{!join score=none from=id fromIndex=collection2 to=field1}*:* > > The question

Re: DateRangeField requires month?

Thanks Mikhail, I think the change you proposed to the documentation will be helpful to avoid this confusion. From: Mikhail Khludnev Sent: Tuesday, January 15, 2019 8:47:17 AM To: solr-user Subject: Re: DateRangeField requires month? Follow up https://issues.apa

RE: join query and new searcher on joined collection

Thanx, Mikhail for reply > collection1 has no idea about new searcher in collection2. I suspected it. :) So, when "join" query arrives searcher on collection1 has no chance to use filter cache, stored before. I suppose it invalidates filter cache, am I right? &fq={!join score=none from=id fromI

Re: join query and new searcher on joined collection

It doesn't invalidate anything. It just doesn't matches to the join query from older collection2 see https://github.com/apache/lucene-solr/blob/b7f99fe55a6fb6e7b38828676750b3512d6899a1/solr/core/src/java/org/apache/solr/search/JoinQParserPlugin.java#L570 So, after commit collection2 following join

Re: Delayed/waiting requests

Well, it was a nice theory anyway. "Other collections with the same settings" doesn't really mean much unless those other collections are very similar, especially in terms of numbers of docs. You should only see a new searcher opening when you do a hard-commit-with-opensearcher-true or soft commi

Re: Re: Delayed/waiting requests

Hi Gael – Could you share this information? Size of the index Server memory available Server CPU count JVM memory settings You mentioned a cloud configuration of 3 replicas. Does that mean you have 1 shard with a replication factor of 3? Do the pauses occur on all 3 servers? Is the traffic evenly

RE: Re: Delayed/waiting requests

@Erick: We will try to lower the autowarm and run some tests to compare. If I get your point, having a big cache might cause more troubles than help if the cache hit ratio is not high enough because the cache is constantly evicting/inserting entries? @Jeremy: Index size: ~20G and ~14M doc

Can Solr 4.10 work with JDK11

I probably already know the answer for this but was still wondering.

Re: Re: Delayed/waiting requests

bq. If I get your point, having a big cache might cause more troubles than help if the cache hit ratio is not high enough because the cache is constantly evicting/inserting entries? Pretty much. Although there are nuances. Right now, you have a 12K autowarm count. That means your cache will event

RE: join query and new searcher on joined collection

I see, thank you very much! > -Original Message- > From: Mikhail Khludnev [mailto:m...@apache.org] > Sent: Tuesday, January 15, 2019 6:45 PM > To: solr-user > Subject: Re: join query and new searcher on joined collection > > It doesn't invalidate anything. It just doesn't matches to the j

Re: Can Solr 4.10 work with JDK11

Or let me rephrase the question. What is the minimum Solr version that is JDK11 compatible. On Tue, Jan 15, 2019 at 10:27 AM Pushkar Raste wrote: > I probably already know the answer for this but was still wondering. >

Re: Delayed/waiting requests

On 1/15/2019 10:33 AM, Gael Jourdan-Weil wrote: Index size: ~20G and ~14M documents Server memory available: 256G from which ~30G used and ~100G system cache Server CPU count: 32, ~10% usage JVM memory settings: -Xms12G -Xmx12G Can you create a process listing screenshot as described at this

Re: Logging fails when starting Solr in Windows using solr.cmd

I faced the same issue as jakob with solr-7.6.0, eclipse-2018-12 (4.10.0), Java 1.8.0_191: *Solution:* In eclipse Run Configuration run-solr remove "file:" from Argument -Dlog4j.configurationFile="file:${workspace_loc:solr-7.6.0}/solr/server/resources/log4j2.xml" -- Sent from: http://lucene.47