https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37020

Thomas Klausner <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #181472|0                           |1
        is obsolete|                            |

--- Comment #58 from Thomas Klausner <[email protected]> ---
Created attachment 181998
  -->
https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=181998&action=edit
Bug 37020: (follow-up): Remove memleak when not using Elasticsearch

If using ES, the script will collect the newly created records and
biblionumbers in atwo arrays (@search_engine_record, @search_engine_record_ids)
and pass that to the indexer when $commitnum records are read. The arrays are
cleaned afterwards.

BUT: The records and biblionumbers were always stored, even if we're not using
Elasticsearch. And as the cleaning of those arrays only happens if we are in
fact using ES, all the data is added but never cleaned.

This patch fixes this by only storing record and biblionumber if we have an
$indexer (i.e. if we're using Elasticsearch).

I have no idea though how/if the records are indexed when using Zebra.

After applying this patch and importing a large enough file without using
Elasticsearch, the RAM usage also stays more or less constant.

@Jan, please verify!

Signed-off-by: Jan Kissig <[email protected]>
Signed-off-by: Thomas Klausner <[email protected]>

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to