<?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 Internal error message: Failed to launch cluster in Kubernetes gcp databricks in Data Governance</title>
    <link>https://community.databricks.com/t5/data-governance/internal-error-message-failed-to-launch-cluster-in-kubernetes/m-p/16713#M595</link>
    <description>&lt;P&gt;we are using data bricks provided default workspace configuration in GCP. we have created 3 gcs buckets and we want to access them by using service principal name through data bricks all-purpose cluster. when we add service principal name in cluster, we are seeing time-out with following error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal error message: Failed to launch cluster in Kubernetes in 1800 seconds. driver readiness:false,last executors readiness ration:1/1 expected executors readiness ratio 0.5 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Spark Startup Failure: Spark was not able to start in time. This issue can be caused by a malfunctioning Hive metastore, invalid Spark configurations, or malfunctioning init scripts. Please refer to the Spark driver logs to troubleshoot this issue, and contact Databricks if the problem persists&lt;/P&gt;</description>
    <pubDate>Thu, 15 Dec 2022 17:00:28 GMT</pubDate>
    <dc:creator>karthik_p</dc:creator>
    <dc:date>2022-12-15T17:00:28Z</dc:date>
    <item>
      <title>Internal error message: Failed to launch cluster in Kubernetes gcp databricks</title>
      <link>https://community.databricks.com/t5/data-governance/internal-error-message-failed-to-launch-cluster-in-kubernetes/m-p/16713#M595</link>
      <description>&lt;P&gt;we are using data bricks provided default workspace configuration in GCP. we have created 3 gcs buckets and we want to access them by using service principal name through data bricks all-purpose cluster. when we add service principal name in cluster, we are seeing time-out with following error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Internal error message: Failed to launch cluster in Kubernetes in 1800 seconds. driver readiness:false,last executors readiness ration:1/1 expected executors readiness ratio 0.5 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Spark Startup Failure: Spark was not able to start in time. This issue can be caused by a malfunctioning Hive metastore, invalid Spark configurations, or malfunctioning init scripts. Please refer to the Spark driver logs to troubleshoot this issue, and contact Databricks if the problem persists&lt;/P&gt;</description>
      <pubDate>Thu, 15 Dec 2022 17:00:28 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/internal-error-message-failed-to-launch-cluster-in-kubernetes/m-p/16713#M595</guid>
      <dc:creator>karthik_p</dc:creator>
      <dc:date>2022-12-15T17:00:28Z</dc:date>
    </item>
    <item>
      <title>Re: Internal error message: Failed to launch cluster in Kubernetes gcp databricks</title>
      <link>https://community.databricks.com/t5/data-governance/internal-error-message-failed-to-launch-cluster-in-kubernetes/m-p/16715#M597</link>
      <description>&lt;P&gt;@Kaniz Fatma​&amp;nbsp;I am trying to raise support ticket, but it is showing admin permission Issue. I am account owner and admin, but still i am unable raise support ticket. whereas if i raise through email it is going to normal priority and not receiving any response. can you please help on that &lt;/P&gt;</description>
      <pubDate>Mon, 19 Dec 2022 15:18:15 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/internal-error-message-failed-to-launch-cluster-in-kubernetes/m-p/16715#M597</guid>
      <dc:creator>karthik_p</dc:creator>
      <dc:date>2022-12-19T15:18:15Z</dc:date>
    </item>
    <item>
      <title>Re: Internal error message: Failed to launch cluster in Kubernetes gcp databricks</title>
      <link>https://community.databricks.com/t5/data-governance/internal-error-message-failed-to-launch-cluster-in-kubernetes/m-p/16716#M598</link>
      <description>&lt;P&gt;Hello @karthik p​&amp;nbsp;, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sorry to send a message in this thread after 3 months, but have you had your issue resolved since then ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are facing the exact same one are still trying to get a hold of the support after 10 days. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Antoine&lt;/P&gt;</description>
      <pubDate>Mon, 06 Mar 2023 16:54:19 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-governance/internal-error-message-failed-to-launch-cluster-in-kubernetes/m-p/16716#M598</guid>
      <dc:creator>Antoine1</dc:creator>
      <dc:date>2023-03-06T16:54:19Z</dc:date>
    </item>
  </channel>
</rss>

