Hi Anny, I am assuming that you perform some complex logic for processing. Can you try to reduce your data size using RDD.sample or RDD.filter before actual processing? That may reduce memory pressure.
Liqaun On Wed, Oct 1, 2014 at 1:53 PM, anny9699 <anny9...@gmail.com> wrote: > Hi Liquan, > > I have 8 workers, each with 15.7GB memory. > > What you said makes sense, but if I don't increase heap space, it keeps > telling me "GC overhead limit exceeded". > > Thanks! > Anny > > On Wed, Oct 1, 2014 at 1:41 PM, Liquan Pei [via Apache Spark User List] > <[hidden > email] <http://user/SendEmail.jtp?type=node&node=15543&i=0>> wrote: > >> Hi >> >> How many nodes in your cluster? It seems to me 64g does not help if each >> of your node doesn't have that many memory. >> >> Liquan >> >> On Wed, Oct 1, 2014 at 1:37 PM, anny9699 <[hidden email] >> <http://user/SendEmail.jtp?type=node&node=15541&i=0>> wrote: >> >>> Hi, >>> >>> After reading some previous posts about this issue, I have increased the >>> java heap space to "-Xms64g -Xmx64g", but still met the >>> "java.lang.OutOfMemoryError: GC overhead limit exceeded" error. Does >>> anyone >>> have other suggestions? >>> >>> I am reading a data of 200 GB and my total memory is 120 GB, so I use >>> "MEMORY_AND_DISK_SER" and kryo serialization. >>> >>> Thanks a lot! >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-spark-user-list.1001560.n3.nabble.com/still-GC-overhead-limit-exceeded-after-increasing-heap-space-tp15540.html >>> Sent from the Apache Spark User List mailing list archive at Nabble.com. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [hidden email] >>> <http://user/SendEmail.jtp?type=node&node=15541&i=1> >>> For additional commands, e-mail: [hidden email] >>> <http://user/SendEmail.jtp?type=node&node=15541&i=2> >>> >>> >> >> >> -- >> Liquan Pei >> Department of Physics >> University of Massachusetts Amherst >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the >> discussion below: >> >> http://apache-spark-user-list.1001560.n3.nabble.com/still-GC-overhead-limit-exceeded-after-increasing-heap-space-tp15540p15541.html >> To unsubscribe from still "GC overhead limit exceeded" after increasing >> heap space, click here. >> NAML >> <http://apache-spark-user-list.1001560.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > > > ------------------------------ > View this message in context: Re: still "GC overhead limit exceeded" > after increasing heap space > <http://apache-spark-user-list.1001560.n3.nabble.com/still-GC-overhead-limit-exceeded-after-increasing-heap-space-tp15540p15543.html> > > Sent from the Apache Spark User List mailing list archive > <http://apache-spark-user-list.1001560.n3.nabble.com/> at Nabble.com. > -- Liquan Pei Department of Physics University of Massachusetts Amherst
