Re: Solr 7.6.0: PingRequestHandler - Changing the default query (*:*)

2019-08-05 Thread Nicolas Franck
If the ping request handler is taking too long, and the server is not recovering automatically, there is not much you can do automatically on that server. You have to intervene manually, and restart Solr on that node. First of all: the ping is just an internal check. If it takes too long to respon

Re: Solr 7.6.0: PingRequestHandler - Changing the default query (*:*)

2019-08-05 Thread Shawn Heisey
On 8/4/2019 10:15 PM, dinesh naik wrote: My question is regarding the custom query being used. Here i am querying for field _root_ which is available in all of my cluster and defined as a string field. The result for _root_:abc might not get me any match as well(i am ok with not finding any match

Difference between search results from Solr 5 and 8

2019-08-05 Thread Alexander Sherbakov
Hi all, We upgraded our Solr cluster from 5 to 8 and I've found a difference in search results. Previously we had this in the schema.xml: Which stopped working in Solr 8, so we mowed this to solrconfig.xml as: AND Now, this search gives 0 results while previously it worked fine and returned 2

Re: Difference between search results from Solr 5 and 8

2019-08-05 Thread Shawn Heisey
On 8/5/2019 7:34 AM, Alexander Sherbakov wrote: Which stopped working in Solr 8, so we mowed this to solrconfig.xml as: AND Now, this search gives 0 results while previously it worked fine and returned 2 records: [ path=select parameters={fq: ["type:Member"], sort: "score desc", q: "u...@gmail.

Re: Solr 7.6.0: PingRequestHandler - Changing the default query (*:*)

2019-08-05 Thread dinesh naik
Hi Nikolas, The restart of node is not helping , the node keeps trying to recover and always fails: here is the log : 2019-07-31 06:10:08.049 INFO (coreZkRegister-1-thread-1-processing-n:replica_host:8983_solr x:parts_shard30_replica_n2697 c:parts s:shard30 r:core_node2698) x:parts_shard30_replic

Re: Solr 7.6.0: PingRequestHandler - Changing the default query (*:*)

2019-08-05 Thread dinesh naik
Hi Shawn, yes i am running solr in cloud mode and Even after adding the params row=0 and distrib=false, the query response is more than 15 sec due to more than a billion doc set. Also the soft commit setting can not be changed to a higher no. due to requirement from business team. http://hostname:

Re: Solr 7.6.0: PingRequestHandler - Changing the default query (*:*)

2019-08-05 Thread Erick Erickson
How much total physical memory on your machine? Lucene holds a lot of the index in MMapDirectory space. My starting point is to allocate no more than 50% of my physical memory to the Java heap. You’re allocating 31G, if you don’t have at _least_ 64G on these machines you’re probably swapping. See:

Re: Solr 7.6.0: PingRequestHandler - Changing the default query (*:*)

2019-08-05 Thread dinesh naik
Hi Erick, Each vm has 128GB of physical memory. On Mon, Aug 5, 2019, 8:38 PM Erick Erickson wrote: > How much total physical memory on your machine? Lucene holds a lot of the > index in MMapDirectory space. My starting point is to allocate no more than > 50% of my physical memory to the Java he

SOLR 8.1.1 index on pdate field included in search results

2019-08-05 Thread Hodder, Rick
I am migrating from SOLR 4.10.2 to 8.1.1. For some reason, in the 8.1.1 core, a pdate index named IDX_ExpirationDate is appearing as a field in the search results documents. I have several other indexes that are defined and (correctly) do not appear in the results. But the index I am having trou

Re: SOLR 8.1.1 index on pdate field included in search results

2019-08-05 Thread Shawn Heisey
On 8/5/2019 10:37 AM, Hodder, Rick wrote: ExpirationDate is supposed to be there, but IDX_ExpirationDate should not. I know that I can probably keep using date, but it is deprecated, and part of the reason for upgrading to 8.1.1 is to use the latest non-deprecated stuff ;-) The DatePointField

RE: SOLR 8.1.1 index on pdate field included in search results

2019-08-05 Thread Hodder, Rick
Hi Shawn, >The DatePointField class defaults to docValues="true" and >useDocValuesAsStored="true". Unless those parameters are changed, >if the field is defined for a document, it will typically be in search results. Just checking, I'm fine with ExpirationDate appearing in the results, it's th

RE: SOLR 8.1.1 index on pdate field included in search results

2019-08-05 Thread Hodder, Rick
You are right of course, Shawn. I added useDocValuesAsStored="false" to the IDX_ExpirationDate field definition, and it no longer shows up Thanks, Rick -Original Message- From: Hodder, Rick Sent: Monday, August 05, 2019 2:02 PM To: solr-user@lucene.apache.org Subject: RE: SOLR 8.1.1 in

Re: NRT for new items in index

2019-08-05 Thread Updates Profimedia
On 2019/08/03 18:00:28, Furkan KAMACI wrote: > Hi, > > First of all, could you check here: > https://lucidworks.com/post/understanding-transaction-logs-softcommit-and-commit-in-sorlcloud/ > to > better understand hard commits, soft commits and transaction logs to > achieve NRT search. > > Ki

Re: NRT for new items in index

2019-08-05 Thread Jörn Franke
Do you have some more information on index and size? Do you have to store everything in the Index? Can you store some data (blobs etc) outside ? I think you are generally right with your solution, but also be aware that it is sometimes cheaper to have several servers instead keeping engineer b