[
https://issues.apache.org/jira/browse/SOLR-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erick Erickson resolved SOLR-613.
---------------------------------
Resolution: Won't Fix
SPRING_CLEANING_2013 We can reopen if necessary
> When a commit fail due to an OutOfMemoryError it doesn't handle properly the
> error (the write.lock is not deleted anymore and the admin adds a new
> document on the update handler for each batch you send).
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-613
> URL: https://issues.apache.org/jira/browse/SOLR-613
> Project: Solr
> Issue Type: Bug
> Components: update
> Affects Versions: 1.2
> Environment: Production
> Reporter: Daniel Alheiros
>
> I'm pushing a lot of documents (committing batches of around 2000 documents)
> and after a while the commit fails due an OutOfMemoryError. Once it happens,
> it's impossible do add any other document because the write.lock file is
> never deleted and notifications cause the update handler to add up one
> document per batch (no matter how many are there) which is misleading.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
