[ANNOUNCEMENT] Luke 6.3.0 released

Download the release zip here: https://github.com/DmitryKey/luke/releases/tag/luke-6.3.0 Upgrade to Lucene 6.3.0. #74 and, other changes in this release: Enjoy!

Re: Memory leak in Solr

On 12/2/2016 12:01 PM, S G wrote: > This post shows some stats on Solr which indicate that there might be a > memory leak in there. > > http://stackoverflow.com/questions/40939166/is-this-a-memory-leak-in-solr > > Can someone please help to debug this? > It might be a very good step in making Solr

CDCR logging messsages

While setting up cdcr on a server I noticed that there were a lot of messages being written to the solr.log. All INFO. 2016-12-02 20:32:59.096 INFO (cdcr-replicator-100-thread-2-processing-n:stlpj1scld.sial.com:8983_solr x:sial-catalog-product_shard1_replica1 s:shard1 c:sial-catalog-product

Re: Memory leak in Solr

Are you sure it's an actual leak, not just memory pinned by caches? Related: https://issues.apache.org/jira/browse/SOLR-9810 On Fri, Dec 2, 2016 at 2:01 PM, S G wrote: > Hi, > > This post shows some stats on Solr which indicate that there might be a > memory leak in

Re: Memory leak in Solr

We’ve been running Solr 4.10.4 in prod for a couple of years. There aren’t any obvious memory leaks in it. It stays up for months. Objects ejected from the cache will almost always be tenured, so that tends to cause full GCs. If there are very few repeats in your query load, you’ll see a lot

Memory leak in Solr

Hi, This post shows some stats on Solr which indicate that there might be a memory leak in there. http://stackoverflow.com/questions/40939166/is-this-a-memory-leak-in-solr Can someone please help to debug this? It might be a very good step in making Solr stable if we can fix this. Thanks SG

Re: Pagination issue

Got it. The problem is tiebreakers. Consider two documents with the same date. Whenever two documents are tied through all the sort criteria you specify then the _internal_ Lucene document ID is used as a tiebreaker. The kicker is that doc1 and doc2 don't have the same internal IDs on replica1

Using DIH FileListEntityProcessor with SolrCloud

Hi all, A question regarding using the DIH FileListEntityProcessor with SolrCloud (solr 6.3.0, zookeeper 3.4.8). I get that the config in SolrCloud lives on the Zookeeper node (a different server from the solr nodes in my setup). With this in mind, where is the baseDir attribute in the

Re: Pagination issue

I think it's related to the sort clause: sort=position_posted_date_id, this is happening only when documents have the same position_posted_date_id, I am not sure what would be the default sort in this case, but depending on which shards is handling the request, I am getting same result but sorted

RE: Schemaless Mode - Multivalued

Yes, the defaults makes sense. I believe I found the chain - . Thanks! Matt -Original Message- From: Alexandre Rafalovitch [mailto:arafa...@gmail.com] Sent: Thursday, December 01, 2016 7:19 PM To: solr-user Subject: Re: Schemaless Mode - Multivalued

Re: Pagination issue

Yes I am sure the uniqueKeyId are unique Here are exactly my two requests: http://SOLR_IP:8201/solr/Staging/select?q=*:*=100=800=id,position_id,job_id=position_posted_date_id%20desc http://SOLR_IP:8201/solr/Staging/select?q=*:*=100=900=id,position_id,job_id=position_posted_date_id%20desc I

RE: Solr seems to reserve facet.limit results

Hello Toke - this is one 6.3 (forgot to mention) and rows=0 and we consume the response in SolrJ. I have not considered streaming as i am still completely unfamiliar with it and i don't yet know what problems it can solve. One simple solution, in my case would be, now just thinking of it, run

Re: Solr seems to reserve facet.limit results

On Fri, 2016-12-02 at 11:21 +, Markus Jelsma wrote: > Despite the number of actual results, queries with a very high > facet.limit are three to five times slower compared to much lower > values. For example, i have a query that returns roughly 19.000 facet > results. Queries with

Solr seems to reserve facet.limit results

Hi - in some cases we want all facets values and counts for a given query, it can be 10k or even 10m but also just one thousand. Despite the number of actual results, queries with a very high facet.limit are three to five times slower compared to much lower values. For example, i have a query

Issue in the analysis chain

Hi, I found a strange behavior with the MappingCharFilterFactory in Solr *6.2.1*. Definitely curious if I'm missing something or someone else met that. I have a (index and query) chain composed as follows: mapping="mapping-FoldToASCII.txt"/> ... The mapping-FoldToASCII.txt is the exact

Re: CDCR: Help With Tlog Growth Issues

Hi Shalin, when the buffer is enabled, tlogs are not removed anymore, even if they were replicated [1]: "When buffering updates, the updates log will store all the updates indefinitely. " Once you disable the buffer, all the old tlogs should be cleaned (the next time the tlog cleaning