Haha, there is a actor-based messaging path that exists between the driver (see ReceiverTracker) and the Receiver (see ReceiverSupervisorImpl). But none of that is exposed to the public API. So either you could hack in Spark Streaming code to expose that, or it might be better to setup you own actor in the custom receiver, and communicate with another actor in the application driver.
Does that make sense? On Thu, Nov 13, 2014 at 5:24 PM, Jacob Abraham <abe.jac...@gmail.com> wrote: > Hi Folks, > > I have written a custom Spark receiver and in my testing I have found that > its doing its job properly. > > However, I am wondering if someone could shed some light on how the "driver" > could query the "receiver" for some information. In other words, how can I > make the driver talk to the receivers to get some information from it ? This > information could be something like the state of the receiver or some > statistics about the receiver itself... > > Regards, > -Abe --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@spark.apache.org For additional commands, e-mail: user-h...@spark.apache.org
