Re: Query of Death Lucene/Solr 7.6

2019-02-22 Thread Michael Gibney
Ah... I think there are two issues likely at play here. One is LUCENE-8531 , which reverts a bug related to SpanNearQuery semantics, causing possible query paths to be enumarated up front. Setting ps=0 (although perhaps not appropriate for some use

Re: Solr Indexes not behaving as expected

2019-02-22 Thread Erick Erickson
You’ll need to look at the solr logs on the machines hosting the collection’s replicas. There should be something more informative there. Is the collection even available for on the target? Can you search anything there? And what’s the reason the collection is being reloaded? If you have “schem

RE: Re: Suppress stack trace in error response

2019-02-22 Thread Markus Jelsma
Hello, Solr's error responses respect the configured response writer settings, so you could probably remove the element and the stuff it contains using XSLT. It is not too fancy, but it should work. Regards, Markus -Original message- > From:Branham, Jeremy (Experis) > Sent: Friday 2

Re: Query of Death Lucene/Solr 7.6

2019-02-22 Thread Gregg Donovan
FWIW: we have also seen serious Query of Death issues after our upgrade to Solr 7.6. Are there any open issues we can watch? Is Markus' findings around `pf` our best guess? We've seen these issues even with ps=0. We also use the WDF. On Fri, Feb 22, 2019 at 8:58 AM Markus Jelsma wrote: > Hello M

Re: Re: Suppress stack trace in error response

2019-02-22 Thread Branham, Jeremy (Experis)
Thanks Edwin – You’re right, I could explain that a bit more. My security team has run a scan against the SOLR servers and identified a few things they want suppressed, one being the stack trace in an error message. For example – 500 1 ` For input string: "`" java.lang.NumberFormatExceptio

Re: Re: Re: Suppress stack trace in error response

2019-02-22 Thread Branham, Jeremy (Experis)
BTW – Congratulations on joining the PMC! Jeremy Branham jb...@allstate.com On 2/22/19, 9:46 AM, "Branham, Jeremy (Experis)" wrote: Thanks Jason – That’s what I was thinking too. It would require some development. Jeremy Branham jb...@allstate.com On 2/22/1

Re: Re: Suppress stack trace in error response

2019-02-22 Thread Branham, Jeremy (Experis)
Thanks Jason – That’s what I was thinking too. It would require some development. Jeremy Branham jb...@allstate.com On 2/22/19, 8:50 AM, "Jason Gerlowski" wrote: Hi Jeremy, Unfortunately Solr doesn't offer anything like what you're looking for, at least that I know of. There

Re: Suppress stack trace in error response

2019-02-22 Thread Jason Gerlowski
Hi Jeremy, Unfortunately Solr doesn't offer anything like what you're looking for, at least that I know of. There's no sort of global "quiet" or "suppressStack" option that you can pass on a request to _not_ get the stacktrace information back. There might be individual APIs which offer somethin

Solr Indexes not behaving as expected

2019-02-22 Thread mrityunjayap
Hi there is strange issue with our Solr Setup in production. We have a cdcr setup. Source machines are working fine. but target Solr is not allowing any operation on existing indexes Solr Version: 6.5.2 Source and Target are configured on 3 linux machines each with 2 shards and 2 replica Below i

RE: Query of Death Lucene/Solr 7.6

2019-02-22 Thread Markus Jelsma
Hello Michael, Sorry it took so long to get back to this, too many things to do. Anyway, yes, we have WDF on our query-time analysers. I uploaded two log files, both the same query of death with and without synonym filter enabled. https://mail.openindex.io/export/solr-8983-console.log 23 MB htt