It looks like 32 bit is affected. > On 2013-08-14 08:27, Dawid Weiss wrote: >> >> Hi everyone, >> >> I am a committer to the Lucene/Solr project. We've recently hit what >> we believe is a JIT/GC bug -- it manifests itself only when G1GC is >> used, on a 32-bit VM:
On Fri, Jan 9, 2015 at 7:10 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 1/1/2015 12:10 PM, Shawn Heisey wrote: > > I've been working with Oracle employees to find better GC tuning > > options. The results are good enough to share with the community: > > > > https://wiki.apache.org/solr/ShawnHeisey#GC_Tuning > > > > With the latest Java 7 or Java 8 version, and a couple of tuning > > options, G1GC has grown up enough to be a viable choice. Two of the > > settings on that list were critical for making the performance > > acceptable with my testing: ParallelRefProcEnabled and G1HeapRegionSize. > > > > I've included some notes on the wiki about how you can size the G1 heap > > regions appropriately for your own index. > > A note was just recently added to the Lucene wiki, saying that the G1 > collector should never be used with Lucene, because there are bugs that > might cause index corruption. Solr uses Lucene, so this would apply. > > > https://wiki.apache.org/lucene-java/JavaBugs#Oracle_Java_.2F_Sun_Java_.2F_OpenJDK_Bugs > > I have never had any problems with it, but perhaps I spoke too soon when > recommending G1. Does anyone else have anything to add? > > Thanks, > Shawn > > -- Bill Bell billnb...@gmail.com cell 720-256-8076
