Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-6678

Collection/core reload is causing a memory leak

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 4.10
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      I have a use case where I need to periodically reload a SolrCloud collection. Recently I did ~1k reload operations and noticed that the cluster was running slower and slower, so I connected to it with jconsole and noticed that heap was growing with every reload operation, forcing GC wasn't helping.

      So I took a heap dump and noticed that I have too many SolrCore-s hanging around.

      It's hard for me to grok the root cause of this, but maybe someone more knowledgable in Solr internals can figure it out by looking into this GC root path (see attached image)? If I interpret this correctly, it looks like one SolrCore is referencing another SolrCore through SolrSuggester. Maybe close hook for SolrSuggester component doesn't release everything that it should be releasing (like SolrSuggester.dictionary)?

        Attachments

        1. ReloadMemoryLeak.png
          179 kB
          Alexey Serba

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                alexey Alexey Serba
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated: