Re: Migration: SOLR8-Java8 -> SOLR8-JAVA11 indexing issue.

Thanks Shawn for checking. As advised we will execute the indexing with the new settings as mentioned and will update the results. Here are the links to missing attachments: Attachment 1: OpenJDK 11 vs OpenJDK 8 key metrics

Re: Migration: SOLR8-Java8 -> SOLR8-JAVA11 indexing issue.

On 10/24/2019 11:50 AM, Junagade, Anup wrote: * Attachment 1: OpenJDK 8 vs OpenJDK 8 key metrics * Attachment 2: OpenJDK 8 vs OpenJDK 8 waiting QTP Threads * Attachment 3: OpenJDK 11 Thread dump There are no attachments. Apache mailing lists swallow almost all attachments.

Solr 8.1.1 Indexing issue while migrating Java8 -> Java11

We are trying to migrate our SOLR 8.1.1 cluster from OpenJDK Java 8 to OpenJDK Java 11 and are facing issues with Indexing. While our indexing is happening flawlessly on Java 8, it crawls or maybe I should say it stalls with Java 11. Any pointers/help is appreciated. *Symptoms* With OpenJDK

Re: Migration: SOLR8-Java8 -> SOLR8-JAVA11 indexing issue.

We are trying to migrate our SOLR 8.1.1 cluster from OpenJDK Java 8 to OpenJDK Java 11 and are facing issues with Indexing. While our indexing is happening flawlessly on Java 8, it crawls or maybe I should say it stalls with Java 11. Any pointers/help is appreciated. Symptoms * With

RE: tlogs are not deleted

Thank you for advice. I will disable it and check if tlogs will disappear. -- Sent from: https://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: solr 8.1.1 many time slower returning query results than solr 4.10.4 or solr 6.5.1

Hi Shawn, Still hoping for some feedback here. Should I not be replying to this thread and instead create a new one? As I do not see an improvement when using java11 I am now going to rebuild again with java8 and solr 8.1.1. Please respond and let me know if I am going in the right direction, or

Re: solr configuration issue

"For every document processed, a soft commit is performed to make the update visible to other concurrent update processes.” Please do not do this! First, Real Time Get will always return the current doc, whether you’ve opened a new reader or not. Second, this is an anti-pattern. I agree with

Re: solr configuration issue

On 10/24/2019 1:52 AM, Danilo Tomasoni wrote: For every document processed, a soft commit is performed to make the update visible to other concurrent update processes. This is not the way to do things. Doing a commit after every document means that Solr will spend more time doing commits

Re: Solr Paryload example

Hi all, just to let you know that we started using spayload function in our quality environment for testing. Within a couple of weeks the feature will be deployed in production. Best regards, Vincenzo On Wed, Oct 23, 2019 at 4:31 PM Vincenzo D'Amore wrote: > Hi Erick, yes, absolutely, it's a

Re: How to update range of dynamic fields in Solr

Hey Arnold, *Now I want to clear any existing ranks before updating with new ones, without having to query what they are first.* Reading the answer of your question, it seems that there are no inbuilt functionality of Solr. Having support of wildcards while indexing could be a nice feature.

Re: copyField - why source should contain * when dest contains *?

Hey Community, I think I have got the answer to my query. This statement about *copyFields *: *The copyField command can use a wildcard (*) character in the dest > parameter only if the source parameter contains one as well.

Re: solr configuration issue

Hi Danilo, We have a solr 7.3.1 instance with around 40 MLN documents in it. I guess you are hard committing after few of millions of docs are indexed, right? I suggest you not to fully avoid hard committing. Set *autoCommit* (not autoSoftCommit) at around half a million of documents (that's

solr configuration issue

Hello all, we have a solr 7.3.1 instance with around 40 MLN documents in it. After the initial one-shot import, we found an issue in the import software, we updated it and re-run the import that will atomically update (with set) the existing documents. The import is divided into processes,

Re: copyField - why source should contain * when dest contains *?

Hey Chris, Awesome explanation. ...then solr has no idea what full field name to use as the destination > when it seees values in a field "foo" ... should it be "1_bar" ? > "aaa_bar" ? ... "z_bar" ? all three? But how does Solr get the idea what full field name to use