spark-instrumented-optimizer/docs/streaming-custom-receivers.md
Chris Fregly 91f9504e60 [SPARK-1981] Add AWS Kinesis streaming support
Author: Chris Fregly <chris@fregly.com>

Closes #1434 from cfregly/master and squashes the following commits:

4774581 [Chris Fregly] updated docs, renamed retry to retryRandom to be more clear, removed retries around store() method
0393795 [Chris Fregly] moved Kinesis examples out of examples/ and back into extras/kinesis-asl
691a6be [Chris Fregly] fixed tests and formatting, fixed a bug with JavaKinesisWordCount during union of streams
0e1c67b [Chris Fregly] Merge remote-tracking branch 'upstream/master'
74e5c7c [Chris Fregly] updated per TD's feedback.  simplified examples, updated docs
e33cbeb [Chris Fregly] Merge remote-tracking branch 'upstream/master'
bf614e9 [Chris Fregly] per matei's feedback:  moved the kinesis examples into the examples/ dir
d17ca6d [Chris Fregly] per TD's feedback:  updated docs, simplified the KinesisUtils api
912640c [Chris Fregly] changed the foundKinesis class to be a publically-avail class
db3eefd [Chris Fregly] Merge remote-tracking branch 'upstream/master'
21de67f [Chris Fregly] Merge remote-tracking branch 'upstream/master'
6c39561 [Chris Fregly] parameterized the versions of the aws java sdk and kinesis client
338997e [Chris Fregly] improve build docs for kinesis
828f8ae [Chris Fregly] more cleanup
e7c8978 [Chris Fregly] Merge remote-tracking branch 'upstream/master'
cd68c0d [Chris Fregly] fixed typos and backward compatibility
d18e680 [Chris Fregly] Merge remote-tracking branch 'upstream/master'
b3b0ff1 [Chris Fregly] [SPARK-1981] Add AWS Kinesis streaming support
2014-08-02 13:35:35 -07:00

7.7 KiB

layout title
global Spark Streaming Custom Receivers

Spark Streaming can receive streaming data from any arbitrary data source beyond the one's for which it has in-built support (that is, beyond Flume, Kafka, Kinesis, files, sockets, etc.). This requires the developer to implement a receiver that is customized for receiving data from the concerned data source. This guide walks through the process of implementing a custom receiver and using it in a Spark Streaming application.

Implementing a Custom Receiver

This starts with implementing a Receiver. A custom receiver must extend this abstract class by implementing two methods

  • onStart(): Things to do to start receiving data.
  • onStop(): Things to do to stop receiving data.

Note that onStart() and onStop() must not block indefinitely. Typically, onStart() would start the threads that responsible for receiving the data and onStop() would ensure that the receiving by those threads are stopped. The receiving threads can also use isStopped(), a Receiver method, to check whether they should stop receiving data.

Once the data is received, that data can be stored inside Spark by calling store(data), which is a method provided by the Receiver class. There are number of flavours of store() which allow you store the received data record-at-a-time or as whole collection of objects / serialized bytes.

Any exception in the receiving threads should be caught and handled properly to avoid silent failures of the receiver. restart(<exception>) will restart the receiver by asynchronously calling onStop() and then calling onStart() after a delay. stop(<exception>) will call onStop() and terminate the receiver. Also, reportError(<error>) reports a error message to the driver (visible in the logs and UI) without stopping / restarting the receiver.

The following is a custom receiver that receives a stream of text over a socket. It treats '\n' delimited lines in the text stream as records and stores them with Spark. If the receiving thread has any error connecting or receiving, the receiver is restarted to make another attempt to connect.

{% highlight scala %}

class CustomReceiver(host: String, port: Int) extends ReceiverString with Logging {

def onStart() { // Start the thread that receives data over a connection new Thread("Socket Receiver") { override def run() { receive() } }.start() }

def onStop() { // There is nothing much to do as the thread calling receive() // is designed to stop by itself isStopped() returns false }

/** Create a socket connection and receive data until receiver is stopped */ private def receive() { var socket: Socket = null var userInput: String = null try { // Connect to host:port socket = new Socket(host, port)

 // Until stopped or connection broken continue reading
 val reader = new BufferedReader(new InputStreamReader(socket.getInputStream(), "UTF-8"))
 userInput = reader.readLine()
 while(!isStopped && userInput != null) {
   store(userInput)
   userInput = reader.readLine()
 }
 reader.close()
 socket.close()

 // Restart in an attempt to connect again when server is active again
 restart("Trying to connect again")
} catch {
 case e: java.net.ConnectException =>
   // restart if could not connect to server
   restart("Error connecting to " + host + ":" + port, e)
 case t: Throwable =>
   // restart if there is any other error
   restart("Error receiving data", t)
}

} }

{% endhighlight %}

{% highlight java %}

public class JavaCustomReceiver extends Receiver {

String host = null; int port = -1;

public JavaCustomReceiver(String host_ , int port_) { super(StorageLevel.MEMORY_AND_DISK_2()); host = host_; port = port_; }

public void onStart() { // Start the thread that receives data over a connection new Thread() { @Override public void run() { receive(); } }.start(); }

public void onStop() { // There is nothing much to do as the thread calling receive() // is designed to stop by itself isStopped() returns false }

/** Create a socket connection and receive data until receiver is stopped */ private void receive() { Socket socket = null; String userInput = null;

try {
  // connect to the server
  socket = new Socket(host, port);

  BufferedReader reader = new BufferedReader(new InputStreamReader(socket.getInputStream()));

  // Until stopped or connection broken continue reading
  while (!isStopped() && (userInput = reader.readLine()) != null) {
    System.out.println("Received data '" + userInput + "'");
    store(userInput);
  }
  reader.close();
  socket.close();

  // Restart in an attempt to connect again when server is active again
  restart("Trying to connect again");
} catch(ConnectException ce) {
  // restart if could not connect to server
  restart("Could not connect", ce);
} catch(Throwable t) {
  // restart if there is any other error
  restart("Error receiving data", t);
}

} }

{% endhighlight %}

Using the custom receiver in a Spark Streaming application

The custom receiver can be used in a Spark Streaming application by using streamingContext.receiverStream(<instance of custom receiver>). This will create input DStream using data received by the instance of custom receiver, as shown below

{% highlight scala %} // Assuming ssc is the StreamingContext val customReceiverStream = ssc.receiverStream(new CustomReceiver(host, port)) val words = lines.flatMap(_.split(" ")) ... {% endhighlight %}

The full source code is in the example CustomReceiver.scala.

{% highlight java %} // Assuming ssc is the JavaStreamingContext JavaDStream customReceiverStream = ssc.receiverStream(new JavaCustomReceiver(host, port)); JavaDStream words = lines.flatMap(new FlatMapFunction<String, String>() { ... }); ... {% endhighlight %}

The full source code is in the example JavaCustomReceiver.java.

Implementing and Using a Custom Actor-based Receiver

Custom Akka Actors can also be used to receive data. The ActorHelper trait can be applied on any Akka actor, which allows received data to be stored in Spark using store(...) methods. The supervisor strategy of this actor can be configured to handle failures, etc.

{% highlight scala %} class CustomActor extends Actor with ActorHelper { def receive = { case data: String => store(data) } } {% endhighlight %}

And a new input stream can be created with this custom actor as

{% highlight scala %} // Assuming ssc is the StreamingContext val lines = ssc.actorStream[String](Props(new CustomActor()), "CustomReceiver") {% endhighlight %}

See ActorWordCount.scala for an end-to-end example.