[jira] Created: (SOLR-613) 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).

["Daniel Alheiros (JIRA)" <ji...@apache.org>]

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.
-
You can reply to this email to add a comment to the issue online.