[
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
good point about recommending 'single' in the event of concurrency bugs.
i've never really looked at the internals of the LockFactories so i'm going to
punt on the subclass idea for now (i like it i just don't have time to do it)
but we can always redefine "single" later. (i'll open another bug if we're
okay with committing this new patch as is)
revised patch just changes the wording and suggested value in solrconfig.xml
objections?
> 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, 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.
