lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shad Storhaug (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (LUCENENET-537) Memory leak while indexing more than 500.000 documents.
Date Thu, 29 Jun 2017 11:02:00 GMT

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

Shad Storhaug closed LUCENENET-537.
-----------------------------------
    Resolution: Cannot Reproduce

Closing as this is now several years old and there wasn't enough information provided to reproduce
the issue. Feel free to reopen if it is still an issue and you want to pursue a solution.

> Memory leak while indexing more than 500.000 documents.
> -------------------------------------------------------
>
>                 Key: LUCENENET-537
>                 URL: https://issues.apache.org/jira/browse/LUCENENET-537
>             Project: Lucene.Net
>          Issue Type: Bug
>          Components: Lucene.Net Core
>    Affects Versions: Lucene.Net 3.0.3
>         Environment: IIS
>            Reporter: Jörg Hubacher
>
> When I'm reindexing a hudge number of documents I've getting an out of memory exception
after some hours.
>                 using (IndexWriter writer = this.CreateIndexWriter(_directory))
>                 {
>                     writer.DeleteAll();
>                     foreach (Product product in _service.GetAllProducts())
>                     {
>                         Document doc = CreateDocument(product);
>                         writer.AddDocument(doc);
>                     }
>                     writer.Commit();
>                     writer.Optimize();
>                 }
> This came up with version 3.0.3. Before it was ok.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message