Thanks Tri,
I really appreciate the response. When I get some free time shortly I'll
start giving some of these a try and report back.
On Mon, Mar 3, 2014 at 12:42 PM, Tri Cao wrote:
> If it's really the interned strings, you could try upgrade JDK, as the
> newer HotSpot
> JVM puts interned st
If it's really the interned strings, you could try upgrade JDK, as the newer HotSpotJVM puts interned strings in regular heap:http://www.oracle.com/technetwork/java/javase/jdk7-relnotes-418459.html(search for String.intern() in that release)I haven't got a chance to look into the new core auto disc
In the user core there are two fields, the database core in question was
40, but in production environments the database core is dynamic. My time
has been pretty crazy trying to get this out the door and we haven't tried
a standard solr install yet but it's on my plate for the test app and I
don't
Hey Josh,I am not an expert in Java performance, but I would start with dumping a the heapand investigate with visualvm (the free tool that comes with JDK).In my experience, the most common cause for PermGen exception is the app createstoo many interned strings. Solr (actually Lucene) interns the
It's a windows installation using a bitnami solr installer. I incorrectly
put 64M into the configuration for this, as I had copied the test
configuration I was using to recreate the permgen issue we were seeing on
our production system (that is configured to 512M) as it takes awhile with
to recreat
Josh,
You've mentioned a couple of times that you've got PermGen set to 512M but then
you say you're running with -XX:MaxPermSize=64M. These two statements are
contradictory so are you *sure* that you're running with 512M of PermGen?
Assuming your on a *nix box can you provide `ps` output provi
Hi;
You can also check here:
http://stackoverflow.com/questions/3717937/cmspermgensweepingenabled-vs-cmsclassunloadingenabled
Thanks;
Furkan KAMACI
2014-02-26 22:35 GMT+02:00 Josh :
> Thanks Timothy,
>
> I gave these a try and -XX:+CMSPermGenSweepingEnabled seemed to cause the
> error to happe
Thanks Timothy,
I gave these a try and -XX:+CMSPermGenSweepingEnabled seemed to cause the
error to happen more quickly. With this option on it didn't seemed to do
any intermittent garbage collecting that delayed the issue in with it off.
I was already using a max of 512MB, and I can reproduce it w
Hi Josh,
Try adding: -XX:+CMSPermGenSweepingEnabled as I think for some VM versions,
permgen collection was disabled by default.
Also, I use: -XX:MaxPermSize=512m -XX:PermSize=256m with Solr, so 64M may be
too small.
Timothy Potter
Sr. Software Engineer, LucidWorks
www.lucidworks.com
___
