Re: Indexing vs Search node

On 11/9/2018 1:58 PM, David Hastings wrote: I personally like standalone solr for this reason, i can tune the indexing "master" for doing nothing but taking in documents and that way the slaves dont battle for resources in the process. SolrCloud can be set up pretty similar to this if you're

Re: Indexing vs Search node

I personally like standalone solr for this reason, i can tune the indexing "master" for doing nothing but taking in documents and that way the slaves dont battle for resources in the process. On Fri, Nov 9, 2018 at 3:10 PM Erick Erickson wrote: > Fernando: > > I'd phrase it more strongly than

Re: Indexing vs Search node

Fernando: I'd phrase it more strongly than Shawn. Prior to 7.0 all replicas both indexed and search (they were NRT replica), so there wasn't any choice but to index and search on every replica. It's one of those things that if you have very high throughput (indexing) situations, you _might_ want

Re: Indexing vs Search node

On 11/9/2018 12:13 PM, Fernando Otero wrote: I read in several blog posts that it's never a good idea to index and search on the same node. I wonder how that can be achieved in Solr Cloud or if it happens automatically. I would disagree with that blanket assertion. Indexing does put

Indexing vs Search node

Hi guys, I read in several blog posts that it's never a good idea to index and search on the same node. I wonder how that can be achieved in Solr Cloud or if it happens automatically. -- Fernando Otero Sr Engineering Manager, Panamera Buenos Aires - Argentina Mobile: +54 911 67697108

Re: Sql server data import

Ok, what that means is you're letting Solr do its best to figure out what fields you should have in the schema and how they're defined. Almost invariably, you can do better by explicitly defining the fields you need in your schema rather than enabling add-unknown. It's fine for getting

Re: Sql server data import

Hello, i managed to fix the problem. I'm using Solr 7.5.0. My problem was that in the server logs i got "This Indexschema is not mutable" (i did not know about the logs folder, so i just found out 5 minutes ago). I fixed it by modifying solrconfig.xml to false*}"

Re: Master Slave Replication Issue

Damian: You say you've switched from 5x to 7x. Did you try to use an index created with 5x or did you index fresh with 7x? Solr/Lucene do not guarantee backward compatibility across more than one major version. Best, Erick On Fri, Nov 9, 2018 at 2:34 AM damian.pawski wrote: > > Hi, > We have

Re: Want to subscribe to this list

Hi Michela, For subscription info see: http://lucene.apache.org/solr/community.html#mailing-lists-irc I'm not aware of any Slack discussion groups, but there are two freenode.net IRC channels - see: http://lucene.apache.org/solr/community.html#irc Steve > On Nov 8, 2018, at 10:42 AM, Michela

Re: Disabling jvm properties from ui

Yes, it is important to understand that only trusted clients and persons should be given access to Solr's port. But it may stil be surprising to users that e.g. passwords to a DB or SSL keystore is available over HTTP when there is no need for them at the client side. I'm not saying itis a

RE: Sql server data import

What is "" in the PublicId? Is it part of the data? Did you check if the special characters in your data cause the problem? Steve ### Error creating document : SolrInputDocument(fields: [PublicId=10065, Id=117]) -Original Message- From: Verthosa Sent: Friday, November 9,

Re: Sql server data import

Which version of Solr is it? Because we have not used schema.xml for a very long time. It has been managed-schema instead. Also, have you tried using DIH example that uses database and modifying it just enough to read data from your database. Even if it has a lot of extra junk, this would test

Sql server data import

Hello, i managed to set up a connection to my sql server to import data into Solr. The idea is to import filetables but for now i first want to get it working using regular tables. So i created *data-config.xml* *schema.xml* i added

Re: Master Slave Replication Issue

Hi, We have switched from 5.4 to 7.2.1 and we have started to see more issues with the replication. I think it may be related to the fact that a delta import was started during a full import (not the case for the Solr 5.4). I am getting below error: XXX:

Re: Negative CDCR Queue Size?

Hi Webster, The queue size "*-1*" suggests the target is not initialized, and you should see a "WARN" in the logs suggesting something bad happened at the respective target. I am also posting the source code for reference. Any chance you can look for WARN in the logs or probably check at