Hello Brief question: How can I clean-up excess files after performing optimize without restarting the Tomcat service?
Detail follows: I've been running several SOLR cores for approx 12 months and have recently noticed the disk usage of one of them is growing considerably faster than the rate at which documents are being added. - 1,200,000 docs 12 months ago used a 45 GB index - 1,700,000 docs today use a 87 GB index - There may have been _some_ deletions, almost certainly <100,000 - The documents are of a broadly uniform style, approx 1000 words So, approximately 45% growth in documents had grown the disk usage by approx 100%. I took a server out of production (I've 1 master & 7 slaves) and did the following. I ran http://server/corename/update?stream.body=<optimize/> on this core which added 49.4 GB to the index folder No previously existing files were deleted I restarted the Tomcat service ONLY the files generated by the optimize remained. All older files were deleted. This is the result I want, but not quite the method I'd prefer. How can I get to this position without restarting the service? Many thanks in advance for any advice you can give This email transmission is confidential and intended solely for the addressee. If you are not the intended addressee, you must not disclose, copy or distribute the contents of this transmission. If you have received this transmission in error, please notify the sender immediately. SThree Management Services Limited. Registered in England and Wales 4255086. Registered office 5th Floor, GPS House, 215-227 Great Portland Street, London, W1W 5PN. http://www.sthree.com
