I think this may be expected. When the streaming context is stopped without the SparkContext, then the receivers are stopped by the driver. The receiver sends back the message that it has been stopped. This is being (probably incorrectly) logged with ERROR level.
On Sun, Aug 9, 2015 at 12:52 AM, Sadaf <sa...@platalytics.com> wrote: > Hi > When i tried to stop spark streaming using ssc.stop(false,true) It gives > the > following error. > > ERROR ReceiverTracker: Deregistered receiver for stream 0: Stopped by > driver > 15/08/07 13:41:11 WARN ReceiverSupervisorImpl: Stopped executor without > error > 15/08/07 13:41:20 WARN WriteAheadLogManager : Failed to write to write > ahead > log > > I've implemented Streaming Listener and a Custom Receiver. Does anyone has > idea about this? > > Thanks :) > > > > > -- > View this message in context: > http://apache-spark-user-list.1001560.n3.nabble.com/ERROR-ReceiverTracker-Deregistered-receiver-for-stream-0-Stopped-by-driver-tp24183.html > Sent from the Apache Spark User List mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscr...@spark.apache.org > For additional commands, e-mail: user-h...@spark.apache.org > >
