Your understanding is correct. If the driver is stuck in GC, then during that period it cannot schedule any tasks.
On Sun, Apr 17, 2016 at 10:27 AM, Rahul Tanwani <tanwanira...@gmail.com> wrote: > Hi Devs, > > In case of stop the world GC events on the driver JVM, since all the > application threads will be stopped, there won't be any new task scheduled > / > launched on the executors. In cases where the full collection is happening, > the applications threads may be stopped for a long time, and if the running > tasks are small, entire cluster will be idle till the GC is over and > application threads are resumed. > > Is my understanding in this regard correct? > > > > -- > View this message in context: > http://apache-spark-developers-list.1001551.n3.nabble.com/Impact-of-STW-GC-events-for-the-driver-JVM-on-overall-cluster-tp17183.html > Sent from the Apache Spark Developers List mailing list archive at > Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org > For additional commands, e-mail: dev-h...@spark.apache.org > >
