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 I fully expect Solr to use up all of the disk space as the collection is more than 50% of the disk volume, how can I cancel this optimize? And separately, if I were to reissue with maxSegments=(high number, eg 40), should I still expect the same disk usage? (I'm presuming so as doesn't it need to gather the whole index to determine which docs should go into which segments?) Solr 4.4 on RHEL6.4, 160GB RAM, 5GB per shard. (Great conference last week btw - so much to learn!) Gil Hoggarth Web Archiving Technical Services Engineer The British Library, Boston Spa, West Yorkshire, LS23 7BQ Tel: 01937 546163
