spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tathagata Das (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-4802) ReceiverInfo removal at ReceiverTracker upon deregistering receiver
Date Tue, 23 Dec 2014 23:25:13 GMT

     [ https://issues.apache.org/jira/browse/SPARK-4802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tathagata Das resolved SPARK-4802.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.1
                   1.1.2
                   1.3.0

> ReceiverInfo removal at ReceiverTracker upon deregistering receiver
> -------------------------------------------------------------------
>
>                 Key: SPARK-4802
>                 URL: https://issues.apache.org/jira/browse/SPARK-4802
>             Project: Spark
>          Issue Type: Bug
>          Components: Streaming
>    Affects Versions: 1.1.0
>            Reporter: Ilayaperumal Gopinathan
>            Priority: Minor
>             Fix For: 1.3.0, 1.1.2, 1.2.1
>
>
> 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,))



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message