Re: Removing old documents

2012-05-01 Thread mav.p...@holidaylettings.co.uk
at are no longer available. So in that case, there's no >update possible. > >On Tue, May 1, 2012 at 8:47 AM, mav.p...@holidaylettings.co.uk < >mav.p...@holidaylettings.co.uk> wrote: > >> Not sure if there is an automatic way but we do it via a delete query >&

Re: Removing old documents

2012-05-01 Thread mav.p...@holidaylettings.co.uk
Not sure if there is an automatic way but we do it via a delete query and where possible we update doc under same id to avoid deletes. On 01/05/2012 13:43, "Bai Shen" wrote: >What is the best method to remove old documents? Things that no generate >404 errors, etc. > >Is there an automatic

Re: commit fail

2012-04-28 Thread mav.p...@holidaylettings.co.uk
.msat java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:485) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:116) On 28/04/2012 02:32, "Yonik Seeley" wrote: >On Fri, Apr 27, 2012 at 8:23 PM, mav.p...@holidaylettings.co.uk > wrote: >&g

commit fail

2012-04-27 Thread mav.p...@holidaylettings.co.uk
Hi again, This is the only log entry I can find, regarding the failed commits… Still timing out as far as the client is concerned and there is actually nothing happening on the server in terms of load (staging environment). 1 CPU core seems busy constantly with solr but unsure what is happening

Re: commit stops

2012-04-27 Thread mav.p...@holidaylettings.co.uk
k and all was ok. I don¹t see any major commit happening at any time, it seems to just hang. Even starting up and shutting down takes ages. We make 3 - 4 commits a day. We use solr 3.5 No autocommit On 28/04/2012 00:56, "Yonik Seeley" wrote: >On Fri, Apr 27, 2012

Re: commit stops

2012-04-27 Thread mav.p...@holidaylettings.co.uk
One more thing I noticed is the the schema browser in the admin interface also eventually times out… Any ideas from anyone ? From: Mav Peri To: "solr-user@lucene.apache.org" mailto:solr-user@lucene.apache.org>> Subject: commit stops Hi We have an index of a

commit stops

2012-04-27 Thread mav.p...@holidaylettings.co.uk
Hi We have an index of about 3.5gb which seems to work fine until it suddenly stops accepting new commits. Users can still search on the front end but nothing new can be committed and it always times out on commit. Any ideas? Thanks in advance 2012-04-27 14:14:20.537:WARN::Committed befor