Minor Description
When the streaming receiver is deregistered, the ReceiverTracker doesn't remove the corresponding receiverInfo entry for the receiver.
When the receiver is stopped at the executor and the ReceiverTrackerActor that processes the 'DeregisterReceiver' message. Shouldn't it remove the receiverInfo entry for that receiver as the receiver is actually deregistered?
Not sure if there is any specific reason for not removing it.
Currently, I see this warning if we don't remove it:
WARN main-EventThread scheduler.ReceiverTracker - All of the receivers have not deregistered, Map(0 -> ReceiverInfo(0,MyReceiver-0,null,false,localhost,Stopped by driver,))
Attachments
Issue Links
- relates to
-
SPARK-2892 Socket Receiver does not stop when streaming context is stopped
-
- Resolved
-
- links to
