On Tue, Jul 20, 2010 at 10:54 PM, Jonathan Gray <[email protected]> wrote: > You think it enough to also include u20 with u18 as not recommended? I > haven't heard anything else about u20 but maybe there's more issues out there. > >> -----Original Message----- >> From: Edward Capriolo [mailto:[email protected]] >> Sent: Tuesday, July 20, 2010 7:49 PM >> To: [email protected] >> Subject: Re: HBase 0.89 and JDK version >> >> On Tue, Jul 20, 2010 at 10:31 PM, Jonathan Gray <[email protected]> >> wrote: >> >> I get lots of sigsegs on u21. Had better luck with u21. >> > >> > Ed, which is the typo? :) >> > >> >> Doh sorry, >> (this was cassandra) I was running. >> -XX:+UseParNewGC \ >> -XX:+UseConcMarkSweepGC \ >> -XX:+CMSParallelRemarkEnabled \ >> -XX:+UseCompressedOops \ >> -XX:SurvivorRatio=8 \ >> -XX:MaxTenuringThreshold=1 \ >> -XX:+HeapDumpOnOutOfMemoryError \ >> with 1.6.0_u20. >> >> I had some data that was causing sigseg as only a a few nodes were >> constantly suffering. I never found what the data was but after moving >> to u21 it never happened again. >
It happened to me, but that does not mean it is a widespread issue. I feel that NoSQL pushes JVMs hard. These type of JVM failures do not end up in your log4j logs typically. I had completely overlooked JVM and was trying to troubleshoot at a much higher level. Switching JVMs can be as simple as moving some symlinks. While I do not believe upgrading/downgrading JVM should be your first recourse for troubleshooting you should consider it at some point. For reference, sigsegv appears multiple times in the 21 bug fix info. http://java.sun.com/javase/6/webnotes/BugFixes6u21.html
