jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chetan Mehrotra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-5995) Lucene indexing with copyonread/write holding unexpectedly much files open
Date Wed, 29 Mar 2017 08:53:41 GMT

    [ https://issues.apache.org/jira/browse/OAK-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15946747#comment-15946747

Chetan Mehrotra commented on OAK-5995:

bq.  Does the size matter? If this is about leaking file handles, what are the circumstances
which impact that behaviour?

I checked the flow and there should not be a leak. But looks like there is. It would depend
upon write frequency

> Lucene indexing with copyonread/write holding unexpectedly much files open
> --------------------------------------------------------------------------
>                 Key: OAK-5995
>                 URL: https://issues.apache.org/jira/browse/OAK-5995
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: lucene
>    Affects Versions: 1.4.1
>            Reporter: Dirk Rudolph
>            Assignee: Chetan Mehrotra
>         Attachments: lsofout2.txt
> We recently faced the issue that our Oak based enterprise content management system run
into failures due to too much open files. Monitoring the lsof output we found out that most
of the opened files of the process are the files within the configured localIndexDir of the
> {code}
> enableCopyOnReadSupport="true"
> localIndexDir="tmp/index"
> enableCopyOnWriteSupport="true"
> {code}
> See attached the lsof output:
> {code}
> ~ wc -l lsofout2.txt
>    20388 lsofout2.txt
> ~ grep "tmp/index" lsofout2.txt | wc -l
>    13499
> {code}
> where more then 60% of open files are "tmp/index" ones as configured as {{localIndexDir}}
shortly after a restart of the process.

This message was sent by Atlassian JIRA

View raw message