lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (JIRA)" <>
Subject [jira] [Updated] (SOLR-2462) Using spellcheck.collate can result in extremely high memory usage
Date Wed, 04 May 2011 17:18:03 GMT


Shawn Heisey updated SOLR-2462:

    Attachment: SOLR-2462_3_1.patch

The original patch would not apply cleanly for me against 3.1 without fuzz and whitespace
options, and when those are used, it applies incorrectly.  Here's a new patch specific to
3.1.  Before creating this, I checked 3.1 out from SVN and then applied the patch for SOLR-2469,
which should not interfere in any way.

Hopefully the patch is suitable.  I am only putting it up here for convenience, in case anyone
else runs into this.

> Using spellcheck.collate can result in extremely high memory usage
> ------------------------------------------------------------------
>                 Key: SOLR-2462
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: spellchecker
>    Affects Versions: 3.1
>            Reporter: James Dyer
>            Priority: Critical
>             Fix For: 3.1.1, 4.0
>         Attachments: SOLR-2462.patch, SOLR-2462_3_1.patch
> When using "spellcheck.collate", class SpellPossibilityIterator creates a ranked list
of *every* possible correction combination.  But if returning several corrections per term,
and if several words are misspelled, the existing algorithm uses a huge amount of memory.
> This bug was introduced with SOLR-2010.  However, it is triggered anytime "spellcheck.collate"
is used.  It is not necessary to use any features that were added with SOLR-2010.
> We were in Production with Solr for 1 1/2 days and this bug started taking our Solr servers
down with "infinite" GC loops.  It was pretty easy for this to happen as occasionally a user
will accidently paste the URL into the Search box on our app.  This URL results in a search
with ~12 misspelled words.  We have "spellcheck.count" set to 15. 

This message is automatically generated by JIRA.
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message