<?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 Troubleshooting Cluster in Administration &amp; Architecture</title>
    <link>https://community.databricks.com/t5/administration-architecture/troubleshooting-cluster/m-p/90956#M1844</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We had a failure on a previously running fact table load (our biggest one) and it looked like an executor was failing due to a timeout error. As a test we upped the cluster size and changed the spark.executor.heartbeatinterval to 300s and the spark.network.timeout to 600s. However the particular job still fails (reporting a "Executor heartbeat timed out after XXXXX ms). Looking further in the logs we noted an error message with the code XXKDA with not a lot of other info. Looking into that error message the dbricks website suggests a bug report is in order, although not sure on that.&lt;/P&gt;&lt;P&gt;Anyone got anything else that we could check? or what the XXKDA error message could mean? We`re currently trying a remedial action of reducing the amount of data (it`s a large merge on a fact table).&lt;/P&gt;</description>
    <pubDate>Wed, 18 Sep 2024 18:24:10 GMT</pubDate>
    <dc:creator>AndySkinner</dc:creator>
    <dc:date>2024-09-18T18:24:10Z</dc:date>
    <item>
      <title>Troubleshooting Cluster</title>
      <link>https://community.databricks.com/t5/administration-architecture/troubleshooting-cluster/m-p/90956#M1844</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We had a failure on a previously running fact table load (our biggest one) and it looked like an executor was failing due to a timeout error. As a test we upped the cluster size and changed the spark.executor.heartbeatinterval to 300s and the spark.network.timeout to 600s. However the particular job still fails (reporting a "Executor heartbeat timed out after XXXXX ms). Looking further in the logs we noted an error message with the code XXKDA with not a lot of other info. Looking into that error message the dbricks website suggests a bug report is in order, although not sure on that.&lt;/P&gt;&lt;P&gt;Anyone got anything else that we could check? or what the XXKDA error message could mean? We`re currently trying a remedial action of reducing the amount of data (it`s a large merge on a fact table).&lt;/P&gt;</description>
      <pubDate>Wed, 18 Sep 2024 18:24:10 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/troubleshooting-cluster/m-p/90956#M1844</guid>
      <dc:creator>AndySkinner</dc:creator>
      <dc:date>2024-09-18T18:24:10Z</dc:date>
    </item>
    <item>
      <title>Re: Troubleshooting Cluster</title>
      <link>https://community.databricks.com/t5/administration-architecture/troubleshooting-cluster/m-p/108685#M2935</link>
      <description>&lt;P&gt;The XXKDA error code is a general indicator for task scheduler issues or &lt;A href="https://github.com/apache/spark/blob/2581ca17eafca0d3f7dccfb3b7900474dab0969e/core/src/test/scala/org/apache/spark/JobCancellationSuite.scala#L213" target="_self"&gt;SPARK_JOB_CANCELLED&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Feb 2025 00:35:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/administration-architecture/troubleshooting-cluster/m-p/108685#M2935</guid>
      <dc:creator>Ismael-K</dc:creator>
      <dc:date>2025-02-04T00:35:46Z</dc:date>
    </item>
  </channel>
</rss>

