Re: Performance & CPU Usage of 6.2.1 vs 6.5.1 & above

As a first guess I would say that you have much higher GC activity which causes much higher CPU usage. Why do you have much higher GC activity? Any GC settings changed? Have you tried increasing heap size? Regards Bernd Am 16.04.2018 um 06:22 schrieb mganeshs: > Solr experts, > > We found

RE: SolrCloud indexing

Hi Shawn, Thank you. I just need to run full indexing due to massive changes in the document. Regards, Moshe Recanati CTO Mobile  + 972-52-6194481 Skype    :  recanati More at:  www.kmslh.com | LinkedIn | FB -Original Message- From: Shawn Heisey Sent: Sunday,

RE: SolrCloud indexing

Hi Erick, Thank you very much. I'll check it out. Regards, Moshe Recanati CTO Mobile  + 972-52-6194481 Skype    :  recanati More at:  www.kmslh.com | LinkedIn | FB -Original Message- From: Erick Erickson Sent: Monday, April 16, 2018 7:01 AM To: solr-user

Performance & CPU Usage of 6.2.1 vs 6.5.1 & above

Solr experts, We found following link where its mentioned like in 6.2.1

Re: SolrCloud indexing

I think you're saying you want to prove out the upgrade in some kind of test setup then switch live traffic. What's commonly used for that is collection aliasing. You just create a new collection and populate it and check it out. When you're satisfied that it's doing what you want, use the

Log reader for target is not initialised

Hello, Over the weekend, we restarted nodes on target and source and after that I see the replication from source to target has stopped and see below warning messages in solr.log. What could be done to resolve this. The leaders on source cluster shows updateLogSynchronizer stoppped while

Re: Appropriate field type for date-without-time

On 4/15/2018 2:31 PM, Christopher Schultz wrote: I'd usually call this a "date", but Solr's documentation says that a "date" is what I would call a timestamp (including time zone). That is correct.  Lucene dates are accurate to the millisecond.  They don't actually handle timezones the way

Re: What is the correct URL for POSTing new data?

On 4/15/2018 2:24 PM, Christopher Schultz wrote: No, it wouldn't have. It doesn't read any configuration files and guesses its way through everything. Simply adding HTTPS support required me to modify the script and manually-specify the URL. That's why I went through the trouble of explaining so

Appropriate field type for date-without-time

ert the date into a number e.g. 20180415 for today and simply store it as a "pint", but that might, ahem, surprise someone looking at documents in the collection and expect that an obvious "date"-oriented field was in fact an int. Also, the year 1 bug will rear its ugly hea

Re: What is the correct URL for POSTing new data?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Shawn, On 4/13/18 6:02 PM, Shawn Heisey wrote: > On 4/13/2018 7:49 AM, Christopher Schultz wrote: >> $ >> SOLR_POST_OPTS="-Djavax.net.ssl.trustStore=/etc/solr/solr-client.p12 >> >> - -Djavax.net.ssl.trustStorePassword=whatevs >>

Re: Solr Reference Guide issue for simplified tokenizers

On 4/15/2018 5:42 AM, Nikolay Khitrin wrote: Given example is class="solr.SimplePatternSplitTokenizerFactory" pattern="[ \t\r\n]+"/> but Lucene's RegExp constructor consumes raw unicode characters instead of \t\r\n form, so correct configuration is Looks like you're right about that

Re: SolrCloud indexing

On 4/15/2018 1:22 AM, Moshe Recanati | KMS wrote: We’re using SolrCloud as part of our product solution for High Availability. During upgrade of a version we need to run full index build on our Solr data. What are you upgrading?  If it's Solr, you should pause/stop indexing while you

Solr Reference Guide issue for simplified tokenizers

I'm feeling I found an issue in Solr Reference Guide for Simplified Regular Expression Pattern [Splitting ]Tokenizer (https://lucene.apache.org/ solr/guide/7_3/tokenizers.html#simplified-regular- expression-pattern-splitting-tokenizer). Given example is but Lucene's RegExp constructor

SolrCloud indexing

Hi, We're using SolrCloud as part of our product solution for High Availability. During upgrade of a version we need to run full index build on our Solr data. I would like to know if as part of SolrCloud we can manage it and make sure that items are available during the index so only once