For capacity planning, our autocomplete gets more than 10X as many
requests as our search. Solr can handle our search just fine, but
I wrote an in-memory prefix match to handle the 25-30M autocomplete
matches each day. I load that by doing Solr queries, so the two
stay in sync.
wunder
On 7/9/08
Hi,
I'm trying to get replication working, and it's failing because commit
refuses to work (at least as I understand it).
I run commit and point it to the update URL. I know the URL is correct,
because solr returns something to me:
commit request to Solr at
Commmit automaticallly does not create snapshots. You must register
the listener to do so
http://wiki.apache.org/solr/CollectionDistribution#head-532ab57f4a3a9cc3ce129a9fb698a01aceb6d0c2
--Noble
On Thu, Jul 10, 2008 at 11:56 AM, Jacob Singh [EMAIL PROTECTED] wrote:
Hi,
I'm trying to get
I don't know much about nagios in particular but I believe there would be
many monitoring tools available which can play nicely with JMX (SOLR-256).
On 7/10/08, Ryan McKinley [EMAIL PROTECTED] wrote:
Is anyone out there using nagios to monitor solr?
I remember some discussion of this in the
Hi all,
I've written a user interface for Solr (Spring web application) which I'd be
willing to donate if people are interested.
You can see a demo here http://larsko.dyndns.org:8080/solr-ui/search.html, SVN
repository is here http://larsko.dyndns.org/svn/solr-ui/. Note in particular
Hi,
I want (if possible) to dedicate one machine only for indexing and to be
optimized only for that.
In solrconfig.xml, I have:
- commented all cache statements
- set to use cold searchers.
- set 1
In the log files I see this all the time:
INFO: Registered new searcher [EMAIL PROTECTED]
Hi,
I just made a commit to http://solrstuff.org/svn/solrjs, containing the
following changes:
A) Build system
The single javascript file became a bit long, so I decided to create a new
directory structure and a small build file:
src/ - single javascript files for every class
lib/ -
Hi,
Solr is working with jetty at port 8983.
I want Solr to send the requets to port 8080.
I have made changes to SimplePostTool.java and changed port 8983 to 8080.
Also made changes in scripts.conf file for port.
still post.jar is looking at port 8983(as i don't know the contents of jar).
Hi,
I have got -Durl= + DEFAULT_POST_URL in the SimplePostTool.java
where the value of DEFAULT_POST_URL, as i had changed it to 8080
public static final String DEFAULT_POST_URL =
http://localhost:8080/solr/updatepublic static final String DEFAULT_POST_URL
= http://localhost:8080/solr/update;
Hi,
Just a add on:
./Solr_Lucene/apache-solr-1.2.0/example/exampledocs
I am executing java -jar post.jar *.xml from above path.
Do i need to copy it into some folder in Tomcat directory?
Thanks,
Sandip Kaur
--- On Thu, 10/7/08, sandeep kaur [EMAIL PROTECTED] wrote:
From: sandeep kaur
It seems you're misunderstanding what -help is saying. You don't
need to change any .java code to change the URL post.jar posts to.
Simply...
java -Durl=http://localhost:8080/solr/update -jar post.jar *.xml
However, if you wish to rebuild post.jar, Solr's Ant build.xml file
will do
Thanks Erik
It has helped.
Please bear with me as i am new to java, tomcat and solr
Best Regards,
Sandip Kaur
--- On Thu, 10/7/08, Erik Hatcher [EMAIL PROTECTED] wrote:
From: Erik Hatcher [EMAIL PROTECTED]
Subject: Re: changing port 8983 to 8080 for Tomcat in solr
To:
Thanks Noble, kya bath hai? Nice Hindi :) Can't read the Thai.
I will look into the listener, but what about the first part of my
question? It says it is failing, but doesn't look like it, but then I
have nothing to go on.
Best,
Jacob
Noble Paul നോബിള് नोब्ळ् wrote:
Commmit automaticallly
Thanks for the responses; I also found this useful thread from back in early
'07:
http://mail-archives.apache.org/mod_mbox/lucene-solr-user/200702.mbox/browser
(the tagging thread), and I might also start looking at facets as an
approach.
However, I'm assuming that facet updates are still just as
Does anyone have a suggestion on a simple restart script. I see
tools like supervise can restart a process when it goes down.
Nagios would be ideal because it can warn you before your solr
instance starts to die - but a simple restart script with an email
alert might be good enough for most.
On
How are you committing? did you use the commit script?
On Thu, Jul 10, 2008 at 7:39 PM, Jacob Singh [EMAIL PROTECTED] wrote:
Thanks Noble, kya bath hai? Nice Hindi :) Can't read the Thai.
Knowing Thai may not help. That is Malayalam
I will look into the listener, but what about the first
Daniel,
I have tested your config of autocomplete. That works perfectly.
THANKS A LOT FOR THAT. Truly appreciate your help.
All,
I am not able to wiki for a lot of the 1.3 filters and analysers. Is
there somewhere that I can get documentation on the same.
-S
Date:
You do, I think. Have a look at DirectUpdateHandler2 class.
On Thu, Jul 10, 2008 at 9:16 PM, Gudata [EMAIL PROTECTED] wrote:
Hi,
I want (if possible) to dedicate one machine only for indexing and to be
optimized only for that.
In solrconfig.xml, I have:
- commented all cache statements
-
Searcher is started anyway. I do not think it is very expensive if the
searcher is not used.
On Thu, Jul 10, 2008 at 11:04 PM, climbingrose [EMAIL PROTECTED] wrote:
You do, I think. Have a look at DirectUpdateHandler2 class.
On Thu, Jul 10, 2008 at 9:16 PM, Gudata [EMAIL PROTECTED] wrote:
Yes I run
bin/commit -u jetty -h localhost -p 8080 -w solr/myclient
I don't use the standard /solr path or standard port, but I don't think
this matters. I know it's hitting the right url, because if I change
the URL, I get other errors, and I am getting XML back (as below).
Best,
Jacob
Noble
On 10-Jul-08, at 4:16 AM, Gudata wrote:
Why Solr is registering new searcher all the time. Is this overhead,
and if
yes, how to stop it?
It is needed for deleteByQuery. Its overhead is negligable if unused.
-Mike
If you have a number of long queries running, your system can become CPU
bound resulting in low throughput and high response times. There are
many ways you can construct a query that will cause it to take a long
time to process, but the SOLR-502 patch can only address the ones where
the work
I didn't know what option was being referred to here, but I eventually
figured it out. If anyone else was confused, the option is called
useFilterForSortedQuery, you can set it via solrconfig.xml, and, at
least according to Yonik in late 2006, you probably won't want to
enable it even if you *do*
: I will look into the listener, but what about the first part of my
: question? It says it is failing, but doesn't look like it, but then I
: have nothing to go on.
This false-negative error message was fixed as part of SOLR-282
-Hoss
: 1. Dynamic sort based on a query
Solr doesn't have anything like this out of the box ... you're going to
need a mapping of input=sort options somewhere, it will most likely be
just as easy to do it in your front end client application, but if you
really want Solr to keep track of that
: I am using the same folder to start solr/ jetty on many local machines
: running same version of linux.
if the same solr + jetty + solr.solr.home combination is working for you
on other machines, then i don't think anyone here can really help you --
sounds like the problem isn't related to
Hi Hoss!
I'll check out from the svn repo. I don't think I can edit it, but
someone should update the wiki page.
Thanks a lot!
Best,
Jacob
Chris Hostetter wrote:
: I will look into the listener, but what about the first part of my
: question? It says it is failing, but doesn't look like it,
: I'll check out from the svn repo. I don't think I can edit it, but
: someone should update the wiki page.
anyone can edit the wiki page if they crete an account ... but i'm not
sure which wiki page you think should be updated -- it's the script that
had the bug in 1.2, and the script was
Hi all,
I have an index with 40 million small records with about 10 fields each.
As my index size grows, I've noticed that queries involving the date field (
range queries, order by, etc) are taking a disproportionately long time.
Could this perhaps be because a date field has so many possible
On 10-Jul-08, at 4:55 PM, Galen Pahlke wrote:
Hi all,
I have an index with 40 million small records with about 10 fields
each.
As my index size grows, I've noticed that queries involving the date
field (
range queries, order by, etc) are taking a disproportionately long
time.
Could this
Oops. Sorry for the typo. I will be careful next time.
Thanks a lot for digging out the old thread :-)
It was helpful.
Should we remove the option useFilterForSortedQuery altogether if its not
being used anymore ?
---
Preetam
On Fri, Jul 11, 2008 at 2:10 AM, Chris Harris [EMAIL PROTECTED]
On Fri, Jul 11, 2008 at 3:11 AM, Chris Hostetter [EMAIL PROTECTED]
wrote:
: I am using the same folder to start solr/ jetty on many local machines
: running same version of linux.
if the same solr + jetty + solr.solr.home combination is working for you
on other machines, then i don't think
32 matches
Mail list logo