Re: Internal details on how ADDREPLICA executes?

Thanks Erick! On Thu, Aug 2, 2018 at 1:26 PM, Erick Erickson wrote: > Oh my, I see confusion on the horizon. _Which_ autoaddreplica? > > Pre 7x and autoscaling, autoAddReplica is all about HDFS and > spinning up a new Solr instance that points to an existing index > so there's no impact on the

Re: Internal details on how ADDREPLICA executes?

Oh my, I see confusion on the horizon. _Which_ autoaddreplica? Pre 7x and autoscaling, autoAddReplica is all about HDFS and spinning up a new Solr instance that points to an existing index so there's no impact on the leader (other than normal peer sync if you're actively indexing). Autoscaling,

Unable To Delete Managed Synonyms Containing a "/" In Solr 7.2

I THINK this might be a bug? I've had troubles with how the Solr Managed Synonym endpoint handles URL encoding of synonyms. It seems to be impossible to delete a synonym which has a forward slash in it. I have a synonym with a key of "Hot/Cold Pack" (that's the key that shows up when I GET the

Internal details on how ADDREPLICA executes?

Hi, I am considering using SolrCloud and enable autoADDREPLICA. I am curious on how long does it take for SolrCloud to setup the replica. Before the new replica can start to serve queries, it needs to copy all the documents in the current leader and also index whatever new traffic is arriving.

SOLRCloud CDCR issue

Hello, Thanks for reading my post! We have the following environment setup: SOLRCloud SOLR Version: 7.3.1 9 Nodes per DC 2 DCs 2 Separate ZK ensemble (one for each SOLR DC) CDCR bidirectional enabled. 2 Collections. 3 shards per collection, 3 replication factors. Basic auth enabled. (Aware of

SolrCloud CDCR issue

Hello, Thanks for reading my post! We have the following environment setup: SOLRCloud SOLR Version: 7.3.1 9 Nodes per DC 2 DCs 2 Separate ZK ensemble (one for each SOLR DC) CDCR bidirectional enabled. 2 Collections. 3 shards per collection, 3 replication factors. Basic auth enabled. (Aware of

Re: SolrQuery Highlight Problem - Not working for text

Does your _text_ field have stored="true"? That's still a requirement for highlighting. the _default managed schema has _text_ as stored="false", so if you just worked from that. Best, Erick On Thu, Aug 2, 2018 at 10:19 AM, THADC wrote: > Hi, we recently upgraded from solr 4.7 to solr

Re: Master recovery in ReplicationHandler

On 8/1/2018 10:05 AM, Chuong Thao wrote: > I am looking to deploy Solr 7.3 in containers with replication handler. Is > there a way to recover the docs on master from the slave if the master is > suddenly killed? Replication in a master-slave setup only goes from master to slave.  It cannot go

Re: Memory Leak in 7.3 to 7.4

Does this script also saves a memory dump of jvm? Ciao, Vincenzo -- mobile: 3498513251 skype: free.dev > On 2 Aug 2018, at 17:53, Erick Erickson wrote: > > Thomas: > > You've obviously done a lot of work to track this, but maybe you can > do even more ;). > > Here's a link to a program that

SolrQuery Highlight Problem - Not working for text

Hi, we recently upgraded from solr 4.7 to solr 7.3. One of the things we had to change for this was the value of text_general type in schema.xml going from "text" to "_text_". Most everywhere things are working fine, except that highlight info is no showing up in our search results performing

Re: Memory Leak in 7.3 to 7.4

Thomas: You've obviously done a lot of work to track this, but maybe you can do even more ;). Here's a link to a program that uses Tika to parse docs _on the client_: https://lucidworks.com/2012/02/14/indexing-with-solrj/ If you take out all the DB and Solr parts, you're left with something

Re: Converting curl request to HTTP URL for Tagger Handler

The error message tells you the issue. You need to POST to the URL, not GET. Check the library you are using and see if you can specify a method there. Most of the libraries do. Regards, Alex. On 2 August 2018 at 11:29, Zheng Lin Edwin Yeo wrote: > Hi, > > I am building up my application

Converting curl request to HTTP URL for Tagger Handler

Hi, I am building up my application using the Tagger Handler in Solr 7.4.0. For the example in the Solr Reference Guide, the query request are done using curl. However, for the actual tagging query, I will need to run it in the HTTP URL in my application. This is the curl query: curl -X POST \

Re: Collection API - ADDREPLICA

I was able to run the collections API after upgrading all the replicas in solr cloud. Thanks, Antony On Wed, Aug 1, 2018 at 4:05 PM, Antony A wrote: > I am running into this bug? > > https://issues.apache.org/jira/browse/SOLR-7055 > > Can we help and let me know if there is a work around? > >

Re: Memory Leak in 7.3 to 7.4

Hi, my final verdict is the upgrade to Tika 1.17. If I downgrade the libraries just for tika back to 1.16 and keep the rest of SOLR 7.4.0 the heap usage after about 85 % of the index process and manual trigger of the garbage collector is about 60-70 MB (That low!!!) My problem now is that we

Re: Memory Leak in 7.3 to 7.4

Hi, SOLR is shipping with a script that handles OOM errors. And produces log files for every case with content like this: Running OOM killer script for process 9015 for Solr on port 28080 Killed process 9015 This script works ;-) kind regards Thomas > Am 02.08.2018 um 12:28 schrieb

Re: Memory Leak in 7.3 to 7.4

Not clear if you had experienced an OOM error. In the meanwhile, if you haven't already added, this can be useful: -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/store/solr-logs/dump.hprof This is my GC_TUNE config - a 32GB server and 16GB reserved for JVM (-Xms16G -Xmx16G) export GC_TUNE="

Memory Leak in 7.3 to 7.4

Hi, we noticed a memory leak in a rather small setup. 40.000 metadata documents with nearly as much files that have „literal.*“ fields with it. While 7.2.1 has brought some tika issues (due to a beta version) the real problems started to appear with version 7.3.0 which are currently unresolved

UnifiedHighlighter not respecting hl.fragsize?

Hi, I'm trying to use UnifiedHighlighter with Solr 7.4.0 and it seem's it's not respecting the hl.fragsize param? I'm expecting the snippet length shouldn't be more than the hl.fragsize value, is that correct? query time params: "hl": "on", "hl.method": "unified" "hl.offsetSource": "POSTINGS"