Re: Solr 7* Sorry, no dataimport-handler defined

Yes I am referring to the dataimport tab in the admin UI and issue SOLR-10035. My previous setup w/ 6.3 did not show this error. I then upgraded to 7.1.0 and the error shows. I upgraded(downgraded) to versions 6.5.0 and 6.6.2 and I do not see the error. Version 7.0.1 also shows the error for me

Solr 7* Sorry, no dataimport-handler defined

I see where this was an issue w/ 6.4 and fixed. I keep getting this error w/ 7.0.1 and 7.1.0. Works fine up until 6.6.2. Could this issue have been reintroduced? Is there somewhere to check what might be going on? I don't see anything in the error logs. -- Sent from: http://lucene.472066.n3

SOLR URL

I'm in the process of upgrading to Solr 5 from Solr 4* using Tomcat w/ multiple webapps. When setting up a SOLR 5 Node is it possible to change the URL From localhost:8080/solr to localhost:8080/whateverIwant ? Another issue to consider w/ this I will have multiple SOLR instances. The way I en

Solr 5 upgrade

Ubuntu 14.04.02 Trying to install solr 5 following this: https://cwiki.apache.org/confluence/display/solr/Upgrading+a+Solr+4.x+Cluster+to+Solr+5.0 I keep getting "this script requires extracting a war file with either the jar or unzip utility, please install these utilities or contact your adminis

Re: Solr 4.3 and above core swap

I commented out the lockType, so it should be using the default of native according to the documentation. There is nothing special about our file systems. Thanks -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-3-and-above-core-swap-tp4084794p4085456.html Sent

Re: Solr 4.3 and above core swap

Thanks for the reply, no nothing else would be writing to the index, I'm sure it is a solrconfig setting but not sure which. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-3-and-above-core-swap-tp4084794p4085091.html Sent from the Solr - User mailing list archive at

Solr 4.3 and above core swap

Since upgrading to solr 4.3 we get the following errors on our slaves when we swap cores on our master and is still an issue on 4.4: Solr index directory '/usr/local/solr_aggregate/solr_aggregate/data/index.20130513152644966' is locked. Throwing exception SEVERE: Unable to reload core: productio

Solr 4.3 core swap

Since upgrading to solr 4.3 we get the following errors on our slaves when we swap cores on our master: Solr index directory '/usr/local/solr_aggregate/solr_aggregate/data/index.20130513152644966' is locked. Throwing exception SEVERE: Unable to reload core: production org.apache.solr.common.Solr

Re: 4.3 logging setup

These are the files I have in my /lib folder: slf4j-api-1.6.6 log4j-1.2.16 jul-to-slf4j-1.6.6 jcl-over-slf4j-1.6.6 slf4j-jdk14-1.6.6 log4j-over-slf4j-1.6.6 Currently everything seems to be logging like before. After I followed the instructions in Jan's post replacing slf4j-log4j12-1.6.6.jar with

Re: 4.3 logging setup

I had already copied those jars over and gotten the app to start(it wouldn't without them). I was able configure solf4j/log4j logging using the log4j.properties in the /lib folder to start logging but I don't want to switch. I have alerts set on the wording that the juli logging puts out but ever

Re: 4.3 logging setup

Thanks for responding. My issue is I've never changed anything w/ logging, I have always used the built in Juli. I've never messed w/ any jar files, just had edit the logging.properties file. I don't know where I would get the jars for juli or where to put them, if that is what is needed. I had

4.3 logging setup

On all prior index version I setup my log via the logging.properties file in /usr/local/tomcat/conf, it looked like this: # Licensed to the Apache Software Foundation (ASF) under one or more # contributor license agreements. See the NOTICE file distributed with # this work for additional informat

Re: Solr 4.1 monitoring with /solr/replication?command=details - indexVersion?

I believe this is the same issue as described, I'm running 4.2 and as you can see my slave is a couple versions ahead of the master (all three slaves show the same behavior). This was never the case until I upgraded from 4.0 to 4.2. Master: 1363272681951 93 1,022.31 MB Slave: 1363273274085 95

Re: Solr 4.0 to Solr 4.1 upgrade

This ended up being a SPM issue. I noticed the same issue w/ 4.2 and decided to upgrade to monitor version 1.9.0 and it is now showing correct data. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-0-to-Solr-4-1-upgrade-tp4044990p4046631.html Sent from the Solr - User

Re: Solr 4.0 to Solr 4.1 upgrade

Otis, I noticed this in my logs repeatedly during that time period: Mar 5, 2013 1:28:00 PM org.apache.solr.core.CachingDirectoryFactory close INFO: Releasing directory:/usr/local/solr_aggregate/solr_aggregate/data/index It wasn't in my logs any other time. I found this: https://issues.apache.o

Solr 4.0 to Solr 4.1 upgrade

I upgrade one of my slaves by replacing the solr.war, all other slaves and master were still 4.0. When I started to monitor it w/ SPM I noticed that the request rate was way up while the request count was way down. I've since put back the solr.war for 4.0 and the slave has returned to normal.

Re: Excluding caching of queryresult

Using cache=false seems to Not be caching the query result. I ran queries against our master server that doesn't get web traffic with and without the parameter and would only notice inserts when the parameter wasn't included. -- View this message in context: http://lucene.472066.n3.nabble.com/E

Re: Excluding caching of queryresult

Thanks Erick, I just found this ticket implying that is able to be used by the main query also: https://issues.apache.org/jira/browse/SOLR-2429 As you stated queryResultCache is cheap, I guess it would nice to get a definitive answer and example

Excluding caching of queryresult

We are aware of adding cache=false to our queries but everything we see seems to reference filterCache. We weren't sure if this parameter would work the same way with the queryResultsCache. Here is an example of a query we don't want to cache(NOTE: I'm just the administrator, I'm not so familiar

Re: High Slave CPU Intermittently After Replication

We started having high load again today a few times today, each time looking at SPM monitor our filter cache starts having high lookups and low hit rate, this is our filtercache setting: would it be possibly too slow? here is the graph when it happens:

Re: Solr 4 Admin UI Dashboard Not Populating

I was able to figure it out, I ran solr/admin/system?wt=xml and noticed that the host entry was blank. Our servers are Linux so I looked at /etc/hosts file and noticed it was messed up. I made the change and everything is populating now. -- View this message in context: http://lucene.472066.n

Solr 4 Admin UI Dashboard Not Populating

Our Admin UI Dashboard is not populating on one of our servers, not sure if it is a permission issue or what. We have three others that it is working on. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-

Re: High Slave CPU Intermittently After Replication

Re: High Slave CPU Intermittently After Replication

We tried using MergeFactor setting but out CPU Load/Slow Query time issues were more widespread, optimizing the index always alleviated the issue that is why we are using it now. Our index is 2 GB when optimized and would balloon to over 4 GB so we thought the issue was it was getting too big. I

High Slave CPU Intermittently After Replication

Here is our setup: Solr 4.0 Master replicates to three slaves after optimize We have a problem were every so often after replication the CPU load on the Slave servers maxes out and request come to a crawl. We do a dataimport every 10 minutes and depending on the number of updates since the las