Return-Path: Delivered-To: apmail-jackrabbit-dev-archive@www.apache.org Received: (qmail 4589 invoked from network); 15 Dec 2010 22:16:36 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Dec 2010 22:16:36 -0000 Received: (qmail 43698 invoked by uid 500); 15 Dec 2010 22:16:35 -0000 Delivered-To: apmail-jackrabbit-dev-archive@jackrabbit.apache.org Received: (qmail 43649 invoked by uid 500); 15 Dec 2010 22:16:35 -0000 Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jackrabbit.apache.org Delivered-To: mailing list dev@jackrabbit.apache.org Received: (qmail 43642 invoked by uid 99); 15 Dec 2010 22:16:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Dec 2010 22:16:35 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Dec 2010 22:16:28 +0000 Received: from joe.nabble.com ([192.168.236.151]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1PSzdn-0000yH-O4 for dev@jackrabbit.apache.org; Wed, 15 Dec 2010 14:16:07 -0800 Date: Wed, 15 Dec 2010 14:16:07 -0800 (PST) From: rabbeet To: dev@jackrabbit.apache.org Message-ID: <1292451367728-3090014.post@n4.nabble.com> In-Reply-To: <1353728499.21265193928596.JavaMail.jira@brutus.apache.org> References: <1353728499.21265193928596.JavaMail.jira@brutus.apache.org> Subject: Re: [jira] Created: (JCR-2483) Out of memory error while adding a new host due to large number of revisions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, this fix is only available as a patch. I am hoping this will get put into a future version. The current implementation does not work for us. We have over 1 million journal records and the current code tries to load all those records into memory when we switch off clustering and rebuild the index. -- View this message in context: http://jackrabbit.510166.n4.nabble.com/jira-Created-JCR-2483-Out-of-memory-error-while-adding-a-new-host-due-to-large-number-of-revisions-tp1461014p3090014.html Sent from the Jackrabbit - Dev mailing list archive at Nabble.com.