You should really try asking on an Atlassian support forum since Jira is their project and they support it. This bug database is for tracking issues about Lucene itself. Also please note that Lucene 3 is many years old now, and no longer receiving bug fixes. The current version is 7, soon to be 8, so even if there is a real issue with that version of Lucene, you are unlikely to get much help with it now.
On Fri, Jul 6, 2018, 5:17 AM changchun huang (JIRA) <[email protected]> wrote: > changchun huang created LUCENE-8389: > --------------------------------------- > > Summary: Could not limit Lucene's memory consumption > Key: LUCENE-8389 > URL: https://issues.apache.org/jira/browse/LUCENE-8389 > Project: Lucene - Core > Issue Type: Bug > Components: core/index > Affects Versions: 3.3 > Environment: |Java Version|1.8.0_102| > |Operating System|Linux 3.12.48-52.27-default| > |Application Server Container|Apache Tomcat/8.5.6| > |atabase JNDI address|mysql > jdbc:mysql://mo-15e744225:3306/jira?useUnicode=true&characterEncoding=UTF8&sessionVariables=default_storage_engine=InnoDB| > |Database version|5.6.27| > |abase driver|MySQL Connector Java mysql-connector-java-5.1.34 ( Revision: > [email protected] )| > |Version|7.6.1| > Reporter: changchun huang > > > We are running Jira 7.6.1 with Lucene 3.3 on SLES 12 SP1 > > We configured 16GB Jira heap on 64GB server > > However, each time, when we run background re-index, the memory will be > used out by Lucene and we could not only limit its memory consumption. > > This definitely will cause overall performance issue on a system with > heavy load. > > We have around 500 concurrent users, 400K issues. > > Could you please help to advice if there were workaround or fix for this? > > Thanks. > > > > BTW: I did check a lot and found a blog introducing the new behavior of > Lucene 3.3 > > [http://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html] > > > > > > -- > This message was sent by Atlassian JIRA > (v7.6.3#76005) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
