Yes, thats a bug i just discovered. Race condition in the Twitter Receiver, will fix asap. Here is the JIRA https://issues.apache.org/jira/browse/SPARK-2464
TD On Sat, Jul 12, 2014 at 3:21 PM, Nicholas Chammas < nicholas.cham...@gmail.com> wrote: > To add a potentially relevant piece of information, around when I stop the > StreamingContext, I get the following warning: > > 14/07/12 22:16:18 WARN ReceiverTracker: All of the receivers have not > deregistered, Map(0 -> > ReceiverInfo(0,TwitterReceiver-0,Actor[akka.tcp://spark@url-here:49776/user/Receiver-0-1405203122224#-273455949],true,url-here-too,,)) > > Nick > > > > On Sat, Jul 12, 2014 at 6:03 PM, Nick Chammas <nicholas.cham...@gmail.com> > wrote: > >> From the interactive shell I’ve created a StreamingContext. >> >> I call ssc.start() and take a look at http://master_url:4040/streaming/ >> and see that I have an active Twitter receiver. Then I call >> 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-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://apache-spark-user-list.1001560.n3.nabble.com/> at Nabble.com. >> > >
