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]
