[ 
https://issues.apache.org/jira/browse/SOLR-4831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13659599#comment-13659599
 ] 

Yonik Seeley edited comment on SOLR-4831 at 5/16/13 2:49 PM:
-------------------------------------------------------------

Looks like the root cause is index corruption.

Could you run check index to verify?
{code}
java -cp ./solr-webapp/webapp/WEB-INF/lib/lucene-core*jar 
-ea:org.apache.lucene... org.apache.lucene.index.CheckIndex 
solr/collection1/data/index
{code}
                
      was (Author: ysee...@gmail.com):
    Looks like the root cause is index corruption.

Could you run check index to verify?
{code}
java -cp ./solr-webapp/webapp/WEB-INF/lib/lucene-core*jar 
-ea:org.apache.lucene... org.apache.lucene.index.CheckIndex 
solr/collection1/index
{code}
                  
> Transaction logs are leaking
> ----------------------------
>
>                 Key: SOLR-4831
>                 URL: https://issues.apache.org/jira/browse/SOLR-4831
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Steven Bower
>
> We have a system in which a client is sending 1 record at a time (via REST) 
> followed by a commit. This has produced ~65k tlog files and the JVM has run 
> out of file descriptors... I grabbed a heap dump from the JVM and I can see 
> ~52k "unreachable" FileDescriptors... This leads me to believe that the 
> TransactionLog is not properly closing all of it's files before getting rid 
> of the object... 
> I've verified with lsof that indeed there are ~60k tlog files that are open 
> currently..
> This is Solr 4.3.0

--
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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to