[
https://issues.apache.org/jira/browse/LUCENE-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794998#action_12794998
]
John Wang commented on LUCENE-2120:
-----------------------------------
Hi Michael:
You are abs. right! By adding an integer increment in the loop made a
difference. From my laptop, I see the break even point at 1.5%.
For what we are using it for in Zoie, the trade-off is worth-while.
Because we rely on Lucene to do the delete check, and use this iteration for
skipping over transient deletes, e.g. the ones that have not been made to the
index. Normally they are << corpus size, e.g. 100 - 1k out of 5M docs. The
memory cost for this is also very small in comparison due to the sparsity of
del docset.
-John
> Possible file handle leak in near real-time reader
> --------------------------------------------------
>
> Key: LUCENE-2120
> URL: https://issues.apache.org/jira/browse/LUCENE-2120
> Project: Lucene - Java
> Issue Type: Bug
> Components: Index
> Affects Versions: 3.1
> Reporter: Michael McCandless
> Assignee: Michael McCandless
> Fix For: 3.1
>
>
> Spinoff of LUCENE-1526: Jake/John hit file descriptor exhaustion when testing
> NRT.
> I've tried to repro this, stress testing NRT, saturating reopens, indexing,
> searching, but haven't found any issue.
> Let's try to get to the bottom of it, here...
--
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
