lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Littlestar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LUCENE-5917) complex Query cause luene outMemory
Date Tue, 02 Sep 2014 03:19:21 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-5917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Littlestar updated LUCENE-5917:
-------------------------------
    Environment: 
256G RAM  + 1.5T SSD + 1.2T DATA(10*10000*10000 records).
java heap=128G, G1


  was:
128G RAM  + 1.5T SSD + 1.2T DATA(10*10000*10000 records).



> complex Query cause luene outMemory
> -----------------------------------
>
>                 Key: LUCENE-5917
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5917
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: core/search
>    Affects Versions: 4.9
>         Environment: 256G RAM  + 1.5T SSD + 1.2T DATA(10*10000*10000 records).
> java heap=128G, G1
>            Reporter: Littlestar
>            Priority: Minor
>
> RangeQuery, prefixQuery and WildcardQuery use FixedBitSet when TERM_COUNT >= 350 or
DOC_COUNT_PERCENT >=0.1.
> It use a lots of memory when maxDoc very large.
> MultiTermQueryWrapperFilter<Q extends MultiTermQuery> extends Filter
> a little threads run with query "a* OR b* OR c*.....OR z*“ will cause luene outMemory,
but there is no ways to prevent it.
> another thing, some complex query also use a lot of memory too..
> I think query implements Accountable(#ramSizeInBytes), users can throw a exception better
than OutOfMemory.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message