So, this problem came up again. Now it only happens in a linux environment
when searches are being conducted while an index is running.
Does anything need to be closed on the searching side?
AgentHubcap wrote:
>
> As it turns out I was modifying code that wasn't being run. Running an
> optimize after deleting did solve my problem. =)
>
>
>
> AgentHubcap wrote:
>>
>> I'm running 1.2.
>>
>> Acutally, i am doing an optimize after I delete the indexes. (twice, as
>> I read there was an issue with the optimize). Do I need to close
>> something manually?
>>
>> Here's my optimize code:
>>
>> private void optimize() throws IOException
>> {
>> UpdateHandler updateHandler =
>> SolrCore.getSolrCore().getUpdateHandler();
>> CommitUpdateCommand commitcmd = new CommitUpdateCommand(false);
>> commitcmd.optimize = true;
>> updateHandler.commit(commitcmd);
>> updateHandler.close();
>> }
>>
>>
>>
>>
>> ryantxu wrote:
>>>
>>>>
>>>> - Delete all index files via a delete command
>>>
>>> make sure to optimize after deleting the docs -- optimize has lucene get
>>> rid of deleted files rather then appending them to the end of the index.
>>>
>>> what version of solr are you running? if you are running 1.3-dev
>>> deleting *:* is fast -- if you aren't using 1.3, i don't suggest moving
>>> there just for that though....
>>>
>>> ryan
>>>
>>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/Index-files-not-being-deleted-tf4512068.html#a13128043
Sent from the Solr - User mailing list archive at Nabble.com.
