Re: LiveListenerBus with started and stopped flags? Why both?

Just to prevent from restarting LiveListenerBus. The internal Thread cannot be restarted. On Wed, May 25, 2016 at 12:59 PM, Jacek Laskowski wrote: > Hi, > > I'm wondering why LiveListenerBus has two AtomicBoolean flags [1]? > Could it not have just one, say started? Why does

LiveListenerBus with started and stopped flags? Why both?

Hi, I'm wondering why LiveListenerBus has two AtomicBoolean flags [1]? Could it not have just one, say started? Why does Spark have to check the stopped state? [1] https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/scheduler/LiveListenerBus.scala#L49-L51