[ 
https://issues.apache.org/jira/browse/SOLR-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hoss Man updated SOLR-240:
--------------------------

    Attachment: IndexWriter2.patch

This is a variation on Will's IndexWriter2.patch that replaces the 
"useNativeLocks" boolean config option with a string config option allowing 
people to pick any of the 4 built in Lucene lock factories.

(i'd been meaning to try and write a "LockFactoryFactory" to allow people to 
specify any arbitrary LockFactory impl as a plugin, but it seemed like overkill 
-- having Will's useNativeLocks option didn't preclude adding something like 
that later, but recent comments reminded me that for the majority of SOlr 
users, the "NoLockFactory" would actually be perfectly fine since Solr only 
ever opens one IndexWriter at a time)

so this patch provides a little bit more flexibility then the previous one, 
without going whole-hog to a FactoryFactory/plugin model.

It should be noted that I left the hardcoded default in the code in to be 
SimpleFSLockFactory but i set the "example" default to be NoLockFactory with a 
comment that that should be find for any Solr user not modifying the index 
externally to Solr.

comments?


> java.io.IOException: Lock obtain timed out: SimpleFSLock
> --------------------------------------------------------
>
>                 Key: SOLR-240
>                 URL: https://issues.apache.org/jira/browse/SOLR-240
>             Project: Solr
>          Issue Type: Bug
>          Components: update
>    Affects Versions: 1.2
>         Environment: windows xp
>            Reporter: Will Johnson
>         Attachments: IndexWriter.patch, IndexWriter2.patch, 
> IndexWriter2.patch, stacktrace.txt, ThrashIndex.java
>
>
> when running the soon to be attached sample application against solr it will 
> eventually die.  this same error has happened on both windows and rh4 linux.  
> the app is just submitting docs with an id in batches of 10, performing a 
> commit then repeating over and over again.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to