[
https://issues.apache.org/jira/browse/LUCENE-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847512#action_12847512
]
Earwin Burrfoot commented on LUCENE-2328:
-----------------------------------------
I'll either jdoc this, or move createOutput to FSDir, as all three current
impls are a copy of each other. In such a case someone overriding createOutput
can look at the original and decide for himself if he wants to keep and call
this functionality, or not.
> When it's opened, not closed, right?
Mike, I thought about it once again. If you allow sync()ing open files, you
still need to track when they are closed. Or the following may happen:
io = dir.createIndexOutput(name); // registers 'name' as a stale file
dir.sync(name) // syncs 'name', removes it from registry
... // do stuff
io.close()
dir.sync(name) // does not sync 'name', as it is no longer in the registry
... // BZZWHAM!!
... // crash happens, the data is lost
> IndexWriter.synced field accumulates data leading to a Memory Leak
> -------------------------------------------------------------------
>
> Key: LUCENE-2328
> URL: https://issues.apache.org/jira/browse/LUCENE-2328
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 2.9.1, 2.9.2, 3.0, 3.0.1
> Environment: all
> Reporter: Gregor Kaczor
> Priority: Minor
> Fix For: 3.1
>
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
