Which garbage collector you are using currently in your env? Can you share the jvm parameters?. If you are using CMS and already optimized your parameter then probably you can look at to G1 garbage collector.
First you should look at the GC stats and pattern to find out the cause of long GC. Regards Jitendra On Thu, Feb 25, 2016 at 3:24 PM, Sandeep Nemuri <[email protected]> wrote: > You my need to tune your GC settings. > > > ᐧ > > On Thu, Feb 25, 2016 at 3:04 PM, Namikaze Minato <[email protected]> > wrote: > >> This happened to us. Our namenodes are on a virtual machine, and >> reducing the number of replication locations of the journal node to >> 1 (it's backed by by a safe raid array anyway) solved the problem. >> >> Regards, >> LLoyd >> >> On 25 February 2016 at 06:39, Gokulakannan M (Engineering - Data >> Platform) <[email protected]> wrote: >> > Hi, >> > >> > It is known that namenode shuts down when a long GC pause happens when >> NN >> > writes edits to journal nodes - Namenode thinks that journal nodes >> didn't >> > respond but actually it was due to the long GC pause. Any pointers on >> > solving this issue? >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > * Regards* > * Sandeep Nemuri* >
