: <fieldtype name="text_lc" class="solr.TextField" tokenized="false">
: <analyzer type="index">
: <tokenizer class="my.custom.TokenizerFactory"/>
: <filter class="my.custom.FilterFactory" words="stopwords.txt"/>
: <filter class="solr.LowerCaseFilterFactory"/>
: <filter class="solr.RemoveDuplicatesTokenFilterFactory"/>
: </analyzer>
: </fieldtype>
...
: only do indexing on the master server. However, with this schema in place
: on the slaves, as well as our custom.jar in the solrHome/lib directory, we
: run into these issues where the memory usage grows and grows without
: explanation.
...even if you only o indexing on the master, having a single analyzer
defined for a field means it's used at both index and query time (even
though you say 'type="index"') so a memory leak in either of your custom
factories could cause a problem on a query box.
This however concerns me...
: fact, in a previous try, we had simply dropped one of our custom plugin jars
: into the lib directory but forgot to deploy the new solrconfig or schema
: files that referenced the classes in there, and the issue still occurred.
...this i can't think of a rational explanation for. Can you elaborate on
what you can do to create this problem .. ie: does the memory usage grow
even when solr doesn't get any requests? or do it happen when searches are
executed? or when commits happen? etc...
If the problem is as easy to reproduce as you describe, can you please
generate some heap dumps against a server that isn't processing any
queries -- one from when hte server first starts up, and one from when hte
server crashes from an OOM (there's a JVM option for generating heap dumps
on OOM that i can't think of off hte top of my head)
-Hoss
