Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <1090147695.1249635074941.JavaMail.jira@brutus>
Date: Fri, 7 Aug 2009 01:51:14 -0700 (PDT)
From: "Jukka Zitting (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Updated: (JCR-1818) Too many open files when merging large
 index segments
In-Reply-To: <291268156.1224150645276.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JCR-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1818:
-------------------------------

    Fix Version/s:     (was: 1.6.0)

The change leveraged java.util.concurrent classes and adapting the code to work in Java 1.4 environments would have been non-trivial. So I simply reverted the change from the 1.x branch in revision 801913. We'll have this only in Jackrabbit 2.0.

> Too many open files when merging large index segments
> -----------------------------------------------------
>
>                 Key: JCR-1818
>                 URL: https://issues.apache.org/jira/browse/JCR-1818
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-core
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 2.0-alpha4
>
>
> When large index segments are merged it may happen that lots of smaller index segments are created but have to wait until the large
> index merge has completed. This may lead to a 'too many open files' exception on some system.
> We should find a solution where large index merges are better decoupled from regular index operations.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.