Hello,
I'm using solr build 2009-06-16_08-06-14, in multicore configuration. When I issue the update command "optimize" to a core, the index files are locked and never released. Calling the coreAdmin unload method on the core unload the core but does not unlock the underlying index files. The core has no other alias, the data path is not referenced by any other core when a full status is requested. The end result is that optimized cores that have been unloaded cannot be deleted until jetty is restarted. I have searched jira but did not find anything relevant. Is this a bug that should be reported, or is this an intended behavior? Thanks, Brian Brian Klippel | Senior Platform Architect 5500 Interstate North Parkway | Atlanta, GA 30328 Office 678.391.7821 <http://www.theport.com/>
