<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Spark is not reading Kinesis Data as fast as specified in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/spark-is-not-reading-kinesis-data-as-fast-as-specified/m-p/46826#M28136</link>
    <description>&lt;P&gt;Hi Databricks community team,&lt;/P&gt;&lt;P&gt;I have code as below&lt;/P&gt;&lt;P&gt;"""&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;df =&lt;/SPAN&gt; &lt;SPAN&gt;spark&lt;/SPAN&gt;&lt;SPAN&gt;.readStream \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.format(&lt;/SPAN&gt;&lt;SPAN&gt;"kinesis"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"endpointUrl"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;endpoint_url&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"streamName"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;stream_name&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"initialPosition"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"latest"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"consumerMode"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"efo"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"maxFetchDuration"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"500ms"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.load()&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;"""&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;With maxFetchDuration, I thought it would fetch data pretty fast. But it felt like it was still doing batch read of multiple seconds. So I added a timestamp to track when it starts to get processed, as well as to trackapproximateArrivalTimestamp from Kinesis:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;"""&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;df = df \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.selectExpr(&lt;/SPAN&gt;&lt;SPAN&gt;"approximateArrivalTimestamp"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"cast (data as STRING) data"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.withColumn(&lt;/SPAN&gt;&lt;SPAN&gt;"processed_timestamp"&lt;/SPAN&gt;&lt;SPAN&gt;, F.current_timestamp()) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.select(F.col(&lt;/SPAN&gt;&lt;SPAN&gt;"approximateArrivalTimestamp"&lt;/SPAN&gt;&lt;SPAN&gt;), F.col(&lt;/SPAN&gt;&lt;SPAN&gt;"processed_timestamp"&lt;/SPAN&gt;&lt;SPAN&gt;), F.from_json(&lt;/SPAN&gt;&lt;SPAN&gt;"data"&lt;/SPAN&gt;&lt;SPAN&gt;, SOME_SCHEMA).alias(&lt;/SPAN&gt;&lt;SPAN&gt;"data_fields"&lt;/SPAN&gt;&lt;SPAN&gt;)) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.select(&lt;/SPAN&gt;&lt;SPAN&gt;'approximateArrivalTimestamp'&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"processed_timestamp"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;'data_fields.*'&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;"""&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;I do satisfy&amp;nbsp;&lt;SPAN class=""&gt;#&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;cores&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;in&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;cluster&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;&amp;gt;=&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;2&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;*&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;(#&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;Kinesis&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;shards)&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;/&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;shardsPerTask -&amp;gt; (8 cores * 4 worker) &amp;gt;= 2 * 64 / 5 -&amp;gt; 32 &amp;gt;= 25.6. I'm using latest Databricks Runtime 14.0 (Spark 3.5.0). This is the only Kinesis consumer to ensure there is no another consumer competing for resource and also got EFO on.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;There is roughly 30 seconds gap between&amp;nbsp;&lt;SPAN&gt;approximateArrivalTimestamp and&amp;nbsp;processed_timestamp consistently. What can I do to lower the gap ?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Attaching evidence of Spark processing in same chunk despite the data arriving to Kinesis few seconds apart.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
    <pubDate>Fri, 29 Sep 2023 15:53:25 GMT</pubDate>
    <dc:creator>938452</dc:creator>
    <dc:date>2023-09-29T15:53:25Z</dc:date>
    <item>
      <title>Spark is not reading Kinesis Data as fast as specified</title>
      <link>https://community.databricks.com/t5/data-engineering/spark-is-not-reading-kinesis-data-as-fast-as-specified/m-p/46826#M28136</link>
      <description>&lt;P&gt;Hi Databricks community team,&lt;/P&gt;&lt;P&gt;I have code as below&lt;/P&gt;&lt;P&gt;"""&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;df =&lt;/SPAN&gt; &lt;SPAN&gt;spark&lt;/SPAN&gt;&lt;SPAN&gt;.readStream \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.format(&lt;/SPAN&gt;&lt;SPAN&gt;"kinesis"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"endpointUrl"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;endpoint_url&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"streamName"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;stream_name&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"initialPosition"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"latest"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"consumerMode"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"efo"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.option(&lt;/SPAN&gt;&lt;SPAN&gt;"maxFetchDuration"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"500ms"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.load()&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;"""&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;With maxFetchDuration, I thought it would fetch data pretty fast. But it felt like it was still doing batch read of multiple seconds. So I added a timestamp to track when it starts to get processed, as well as to trackapproximateArrivalTimestamp from Kinesis:&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;"""&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;df = df \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.selectExpr(&lt;/SPAN&gt;&lt;SPAN&gt;"approximateArrivalTimestamp"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"cast (data as STRING) data"&lt;/SPAN&gt;&lt;SPAN&gt;) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.withColumn(&lt;/SPAN&gt;&lt;SPAN&gt;"processed_timestamp"&lt;/SPAN&gt;&lt;SPAN&gt;, F.current_timestamp()) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.select(F.col(&lt;/SPAN&gt;&lt;SPAN&gt;"approximateArrivalTimestamp"&lt;/SPAN&gt;&lt;SPAN&gt;), F.col(&lt;/SPAN&gt;&lt;SPAN&gt;"processed_timestamp"&lt;/SPAN&gt;&lt;SPAN&gt;), F.from_json(&lt;/SPAN&gt;&lt;SPAN&gt;"data"&lt;/SPAN&gt;&lt;SPAN&gt;, SOME_SCHEMA).alias(&lt;/SPAN&gt;&lt;SPAN&gt;"data_fields"&lt;/SPAN&gt;&lt;SPAN&gt;)) \&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;.select(&lt;/SPAN&gt;&lt;SPAN&gt;'approximateArrivalTimestamp'&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;"processed_timestamp"&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN&gt;'data_fields.*'&lt;/SPAN&gt;&lt;SPAN&gt;)&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;"""&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;I do satisfy&amp;nbsp;&lt;SPAN class=""&gt;#&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;cores&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;in&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;cluster&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;&amp;gt;=&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;2&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;*&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;(#&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;Kinesis&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;shards)&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;/&lt;/SPAN&gt;&amp;nbsp;&lt;SPAN class=""&gt;shardsPerTask -&amp;gt; (8 cores * 4 worker) &amp;gt;= 2 * 64 / 5 -&amp;gt; 32 &amp;gt;= 25.6. I'm using latest Databricks Runtime 14.0 (Spark 3.5.0). This is the only Kinesis consumer to ensure there is no another consumer competing for resource and also got EFO on.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;There is roughly 30 seconds gap between&amp;nbsp;&lt;SPAN&gt;approximateArrivalTimestamp and&amp;nbsp;processed_timestamp consistently. What can I do to lower the gap ?&lt;/SPAN&gt;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;SPAN&gt;Attaching evidence of Spark processing in same chunk despite the data arriving to Kinesis few seconds apart.&lt;/SPAN&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 29 Sep 2023 15:53:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/spark-is-not-reading-kinesis-data-as-fast-as-specified/m-p/46826#M28136</guid>
      <dc:creator>938452</dc:creator>
      <dc:date>2023-09-29T15:53:25Z</dc:date>
    </item>
  </channel>
</rss>

