Thanks Mike, Got my sysadmins to upgrade our test machine to "1.7.0_09" Will ask them to upgrade production which is currently 1.6.0_45-b06 on the indexing machines and 1.6.0_16-b01 on the serving machines.
Tom On Tue, Jul 30, 2013 at 1:47 PM, Michael McCandless < luc...@mikemccandless.com> wrote: > You should also upgrade your Java! > > 1.6.0_16 is really ancient and has exciting bugs ... > > Mike McCandless > > http://blog.mikemccandless.com > > > On Tue, Jul 30, 2013 at 1:06 PM, Tom Burton-West <tburt...@umich.edu> > wrote: > > Thanks Mike, Robert and Adrien, > > > > Unfortunately, I killed the processes, so its too late to get a stack > > trace. On thing that was suspicious was that top was reporting memory > use > > as 20GB res even though I invoked the JVM with java -Xmx10g -Xms10g. > > > > I'm going to double the memory, turn on GC logging, and remember to echo > > STDERR to a log and run it again on one of the indexes. > > I'll report back as soon as something interesting shows up. (Probably > > tomorrow sometime.) > > > > Tom > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > >
