Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of gkaczor@gmx.de designates
 213.165.64.20 as permitted sender)
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 17 Mar 2010 19:15:47 +0100
From: "Gregor Kaczor" <gkaczor@gmx.de>
Message-ID: <20100317181547.90050@gmx.net>
MIME-Version: 1.0
Subject: IndexWriter.synced field accumulates data
To: java-dev@lucene.apache.org
Content-Transfer-Encoding: 7bit

I am running into a strange OutOfMemoryError. My small test application does index and delete some few files. This is repeated for 60k times.  Optimization is run from every 2k times a file is indexed. Index size is 50KB. I did analyze the HeapDumpFile and realized that IndexWriter.synced field occupied more than half of the heap. That field is a private HashSet without a getter. Its task is to hold files which have been synced already. 

There are two calls to addAll and one call to add on synced but no remove or clear throughout the lifecycle of the IndexWriter instance. 

According to the Eclipse Memory Analyzer synced contains 32618 entries which look like file names "_e065_1.del" or "_e067.cfs" 

The index directory contains 10 files only.

I guess synced is holding obsolete data

---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org