On Mon, Nov 11, 2013 at 11:28 AM, Hoggarth, Gil wrote:
> I could stop the whole Solr service as
> as yet there's no audience access to it, but might it be left in an
> incomplete state and thus try to complete optimisation when the service
> is restarted?
Should be fine.
Lucene has a write-once
oring
service! Must set up the demo version, asap!]
-Original Message-
From: Otis Gospodnetic [mailto:otis.gospodne...@gmail.com]
Sent: 11 November 2013 16:02
To: solr-user@lucene.apache.org
Subject: Re: How to cancel a collection 'optimize'?
Hi Gil,
(we spoke in Dublin, didn
Hi Gil,
(we spoke in Dublin, didn't we?)
Short of stopping Solr I have a feeling there isn't much you can
do hm. or, I wonder if you could somehow get a thread dump,
get the PID of the thread (since I believe threads in Linux are run as
processes), and then kill that thread... Feels scary
We have an internal Solr collection with ~1 billion documents. It's
split across 24 shards and uses ~3.2TB of disk space. Unfortunately
we've triggered an 'optimize' on the collection (via a restarted browser
tab), which has raised the disk usage to 4.6TB, with 130GB left on the
disk volume.
As