Spark Streaming allows you to use Spark for stream processing. You write a streaming job the same way as you would write a Map job. At execution time, Spark breaks the input stream into a series of small jobs and runs them in batches. Inputs can come from sources such as HDFS, Kafka, Kinesis, Flume, and others. A typical output destination would be a file system, a database, or a dashboard.
Kinesis and Kafka client jars are available in Qubole Spark as part of the basic package.
Running Spark Streaming on QDS¶
You can run Spark Streaming jobs on a Qubole Spark cluster either from the Analyze page or Notebooks page of QDS.
For more information, see Composing Spark Commands in Different Spark Languages through the UI and Running Spark Applications in Notebooks.
You should be aware of the following considerations when running Spark Streaming jobs:
Qubole recommends Spark on Yarn in client mode for Streaming; this is the QDS default.
Qubole has a 36-hour time limit on every command run. For streaming applications this limit can be removed. Contact Qubole Support to remove this limit.
If your application needs to receive multiple streams of data in parallel, create multiple input DStreams. This will create multiple receivers which will simultaneously receive multiple data streams. (But note the points about sizing and resources that follow.)
QDS supports basic version of open-source streaming dynamic allocation for Spark streaming applications. The open-source streaming dynamic allocation is available only in Spark 2.0 and later versions. Based on the processing time required by the tasks, executors are added/downscaled. However, executors with receivers are never removed. By default, autoscaling is disabled on Spark streaming applications. Set
spark.streaming.dynamicAllocation.enabled=trueto enable autoscaling in Spark streaming applications.
Ensure to set
spark.dynamicAllocation.enabled=falsewhen you set
spark.streaming.dynamicAllocation.enabled=trueas an appropriate error is thrown if both the settings are enabled.
These practices are recommended for better autoscaling:
- It is best to start with a fairly large cluster and number of executors and scale down if necessary. (An executor maps to a YARN container.)
- The number of executors should be at least equal to the number of receivers.
- Set the number of cores per executor such that the executor has some spare capacity over and above what’s needed to run the receiver.
- The total number of cores must be greater than the number of receivers; otherwise the application will not be able to process the data it receives.
trueallows Spark Streaming to control the receiving rate (on the basis of current batch scheduling delays and processing times) so that the system receives data only as fast as it can process it.
For the best performance, consider using the Kryo Serializer to convert between serialized and deserialized representations of Spark data. This is not the Spark default, but you can change it explicitly: set the
Developers can reduce memory consumption by un-caching DStreams when they are no longer needed.