一文讀懂 超簡單的spark structured stream 源碼解讀

為了讓大家理解structured stream的運行流程，我將根據一個代碼例子，講述structured stream的基本運行流程和原理。

下面是一段簡單的代碼:

val spark = SparkSession
      .builder
      .appName("StructuredNetworkWordCount")
      .master("local[4]")

      .getOrCreate()
    spark.conf.set("spark.sql.shuffle.partitions", 4)

    import spark.implicits._
    val words = spark.readStream
      .format("socket")
      .option("host", "localhost")
      .option("port", 9999)
      .load()

    val df1 = words.as[String]
      .flatMap(_.split(" "))
      .toDF("word")
      .groupBy("word")
      .count()

    df1.writeStream
      .outputMode("complete")
      .format("console")
      .trigger(ProcessingTime(10))
      .start()

    spark.streams.awaitAnyTermination()

 

　　這段代碼就是單詞計數。先從一個socket數據源讀入數據，然后以" " 為分隔符把一行文本轉換成單詞的DataSet，然后轉換成有標簽("word")的DataFrame，接着按word列進行分組，聚合計算每個word的個數。最后輸出到控制台，以10秒為批處理執行周期。

　　

現在來分析它的原理。spark的邏輯里面有一個惰性計算的概念，以上面的例子來說，在第22行代碼以前，程序都不會對數據進行真正的計算，而是將計算的公式（或者函數）保存在DataFrame里面，在22行開始的writeStream.start調用后才開始真正的計算。為什么？

因為：

這可以讓spark內核做一些優化。

例如：

數據庫中存放着人的名字和年齡，我想要在控制台打印出前十個年齡大於20歲的人的名字，那么我的spark代碼會這么寫：

df.fileter{row=>
row._2>20}
.show(10)

假如說我每執行一行代碼就進行一次計算，那么在第二行的時候，我就會把df里面所有的數據進行過濾，篩選出其中年齡大於20的，然后在第3行執行的時候，從第2行里面的結果中選前面10個進行打印。

看出問題了么？這里的輸出僅僅只需要10個年齡大於20的人，但是我卻把所有人都篩選了一遍，其實我只需要篩選出10個，后面的就不必要篩選了。這就是spark的惰性計算進行優化的地方。

在spark的計算中，在真正的輸出函數之前，都不會進行真正的計算，而會在輸出函數之前進行優化后再進行計算。我們來看源代碼。

這里我貼的是structured stream每次批處理周期到達時會運行的代碼:

 private def runBatch(sparkSessionToRunBatch: SparkSession): Unit = {
    // Request unprocessed data from all sources.
    newData = reportTimeTaken("getBatch") {
      availableOffsets.flatMap {
        case (source, available)
          if committedOffsets.get(source).map(_ != available).getOrElse(true) =>
          val current = committedOffsets.get(source)
          val batch = source.getBatch(current, available)
          logDebug(s"Retrieving data from $source: $current -> $available")
          Some(source -> batch)
        case _ => None
      }
    }

    // A list of attributes that will need to be updated.
    var replacements = new ArrayBuffer[(Attribute, Attribute)]
    // Replace sources in the logical plan with data that has arrived since the last batch.
    val withNewSources = logicalPlan transform {
      case StreamingExecutionRelation(source, output) =>
        newData.get(source).map { data =>
          val newPlan = data.logicalPlan
          assert(output.size == newPlan.output.size,
            s"Invalid batch: ${Utils.truncatedString(output, ",")} != " +
            s"${Utils.truncatedString(newPlan.output, ",")}")
          replacements ++= output.zip(newPlan.output)
          newPlan
        }.getOrElse {
          LocalRelation(output)
        }
    }

    // Rewire the plan to use the new attributes that were returned by the source.
    val replacementMap = AttributeMap(replacements)
    val triggerLogicalPlan = withNewSources transformAllExpressions {
      case a: Attribute if replacementMap.contains(a) => replacementMap(a)
      case ct: CurrentTimestamp =>
        CurrentBatchTimestamp(offsetSeqMetadata.batchTimestampMs,
          ct.dataType)
      case cd: CurrentDate =>
        CurrentBatchTimestamp(offsetSeqMetadata.batchTimestampMs,
          cd.dataType, cd.timeZoneId)
    }

    reportTimeTaken("queryPlanning") {
      lastExecution = new IncrementalExecution(
        sparkSessionToRunBatch,
        triggerLogicalPlan,
        outputMode,
        checkpointFile("state"),
        currentBatchId,
        offsetSeqMetadata)
      lastExecution.executedPlan // Force the lazy generation of execution plan
    }

    val nextBatch =
      new Dataset(sparkSessionToRunBatch, lastExecution, RowEncoder(lastExecution.analyzed.schema))

    reportTimeTaken("addBatch") {
      sink.addBatch(currentBatchId, nextBatch)
    }

    awaitBatchLock.lock()
    try {
      // Wake up any threads that are waiting for the stream to progress.
      awaitBatchLockCondition.signalAll()
    } finally {
      awaitBatchLock.unlock()
    }
  }

其實很簡單，在第58以前都是在解析用戶代碼，生成logicPlan，優化logicPlan，生成批處理類。第47行的triggerLogicalPlan就是最終優化后的用戶邏輯，它被封裝在了一個IncrementalExecution類中，這個類連同sparkSessionToRunBatch（運行環境）和RowEncoder（序列化類）一起構成一個新的DataSet，這個DataSet就是最終要發送到worker節點進行執行的代碼。第59行代碼就是在將它加入到准備發送代碼的隊列中。我們繼續看一段代碼，由於我們使用console作為數據下游（sink）所以看看console的addBatch代碼：

override def addBatch(batchId: Long, data: DataFrame): Unit = synchronized {
    val batchIdStr = if (batchId <= lastBatchId) {
      s"Rerun batch: $batchId"
    } else {
      lastBatchId = batchId
      s"Batch: $batchId"
    }

    // scalastyle:off println
    println("-------------------------------------------")
    println(batchIdStr)
    println("-------------------------------------------")
    // scalastyle:off println
    data.sparkSession.createDataFrame(
      data.sparkSession.sparkContext.parallelize(data.collect()), data.schema)
      .show(numRowsToShow, isTruncated)
  }

關鍵代碼在16行.show函數，show函數是一個真正的action，在這之前都是一些算子的封裝，我們看show的代碼:

private[sql] def showString(_numRows: Int, truncate: Int = 20): String = {
    val numRows = _numRows.max(0)
    val takeResult = toDF().take(numRows + 1)
    val hasMoreData = takeResult.length > numRows
    val data = takeResult.take(numRows)

第3行進入take:

  def take(n: Int): Array[T] = head(n)

def head(n: Int): Array[T] = withAction("head", limit(n).queryExecution)(collectFromPlan)

private def withAction[U](name: String, qe: QueryExecution)(action: SparkPlan => U) = {
    try {
      qe.executedPlan.foreach { plan =>
        plan.resetMetrics()
      }
      val start = System.nanoTime()
      val result = SQLExecution.withNewExecutionId(sparkSession, qe) {
        action(qe.executedPlan)
      }
      val end = System.nanoTime()
      sparkSession.listenerManager.onSuccess(name, qe, end - start)
      result
    } catch {
      case e: Exception =>
        sparkSession.listenerManager.onFailure(name, qe, e)
        throw e
    }
  }

這個函數名就告訴我們，這是真正計算要開始了，第7行代碼一看就是准備發送代碼序列了:

def withNewExecutionId[T](
      sparkSession: SparkSession,
      queryExecution: QueryExecution)(body: => T): T = {
    val sc = sparkSession.sparkContext
    val oldExecutionId = sc.getLocalProperty(EXECUTION_ID_KEY)
    if (oldExecutionId == null) {
      val executionId = SQLExecution.nextExecutionId
      sc.setLocalProperty(EXECUTION_ID_KEY, executionId.toString)
      executionIdToQueryExecution.put(executionId, queryExecution)
      val r = try {
        // sparkContext.getCallSite() would first try to pick up any call site that was previously
        // set, then fall back to Utils.getCallSite(); call Utils.getCallSite() directly on
        // streaming queries would give us call site like "run at <unknown>:0"
        val callSite = sparkSession.sparkContext.getCallSite()

        sparkSession.sparkContext.listenerBus.post(SparkListenerSQLExecutionStart(
          executionId, callSite.shortForm, callSite.longForm, queryExecution.toString,
          SparkPlanInfo.fromSparkPlan(queryExecution.executedPlan), System.currentTimeMillis()))
        try {
          body
        } finally {
          sparkSession.sparkContext.listenerBus.post(SparkListenerSQLExecutionEnd(
            executionId, System.currentTimeMillis()))
        }
      } finally {
        executionIdToQueryExecution.remove(executionId)
        sc.setLocalProperty(EXECUTION_ID_KEY, null)
      }
      r
    } else {
      // Don't support nested `withNewExecutionId`. This is an example of the nested
      // `withNewExecutionId`:
      //
      // class DataFrame {
      //   def foo: T = withNewExecutionId { something.createNewDataFrame().collect() }
      // }
      //
      // Note: `collect` will call withNewExecutionId
      // In this case, only the "executedPlan" for "collect" will be executed. The "executedPlan"
      // for the outer DataFrame won't be executed. So it's meaningless to create a new Execution
      // for the outer DataFrame. Even if we track it, since its "executedPlan" doesn't run,
      // all accumulator metrics will be 0. It will confuse people if we show them in Web UI.
      //
      // A real case is the `DataFrame.count` method.
      throw new IllegalArgumentException(s"$EXECUTION_ID_KEY is already set")
    }
  }

你看第16行，就是在發送數據，包括用戶優化后的邏輯，批處理的id，時間戳等等。worker接收到這個事件后根據logicalPlan里面的邏輯就開始干活了。這就是一個很基本很簡單的流程，對於spark入門還是挺有幫助的吧。