[
https://issues.apache.org/jira/browse/LUCENE-5462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907030#comment-13907030
]
Robert Muir commented on LUCENE-5462:
-------------------------------------
+1, i'm the culprit here. the whole reason for the size estimation method, was
that just calling RUE on segmentcorereaders or whatever in my tests was wayy
too slow.
In general there might be more issues than Lucene3xFields. For older deprecated
codecs, I "cheated" and used this method, instead of trying to properly
implement it... because they were just for back compat. But I can see how an
app would use the method, yet still have some old segments...
> Lucene3xFields shouldn't use RamUsageEstimator to estimate size
> ---------------------------------------------------------------
>
> Key: LUCENE-5462
> URL: https://issues.apache.org/jira/browse/LUCENE-5462
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Fix For: 4.7
>
>
> We have had a few Elasticsearch users who have high CPU usage because of
> RamUsageEstimator being used to estimate memory usage of Lucene3xFields.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
