I'm running on spark 1.0.0 and I see a similar problem when using the
socketTextStream receiver. The ReceiverTracker task sticks around after a
ssc.stop(false).
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Stopping-StreamingContext-does-not-kill-receiver
the
socketTextStream receiver. The ReceiverTracker task sticks around after a
ssc.stop(false).
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Stopping-StreamingContext-does-not-kill-receiver-tp9522p11587.html
Sent from the Apache Spark User List mailing list
/Screen_Shot_2014-08-06_at_4.png
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Stopping-StreamingContext-does-not-kill-receiver-tp9522p11595.html
Sent from the Apache Spark User List mailing list archive at Nabble.com
active.
Is this expected? I’m running 1.0.1 on EC2.
Nick
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Stopping-StreamingContext-does-not-kill-receiver-tp9522.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
ssc.stop(stopSparkContext
= false, stopGracefully = true) and wait a bit, but the receiver seems
to stay active.
Is this expected? I’m running 1.0.1 on EC2.
Nick
--
View this message in context: Stopping StreamingContext does not kill
receiver
http://apache
--
View this message in context: Stopping StreamingContext does not kill
receiver
http://apache-spark-user-list.1001560.n3.nabble.com/Stopping-StreamingContext-does-not-kill-receiver-tp9522.html
Sent from the Apache Spark User List mailing list archive
http
