<?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 Re: SQL Databricks - Spot VMs (Cost Optimized) in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28307#M20130</link>
    <description>&lt;P&gt;I agree with you&lt;/P&gt;</description>
    <pubDate>Tue, 15 Feb 2022 12:36:04 GMT</pubDate>
    <dc:creator>Gvsmao</dc:creator>
    <dc:date>2022-02-15T12:36:04Z</dc:date>
    <item>
      <title>SQL Databricks - Spot VMs (Cost Optimized)</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28300#M20123</link>
      <description>&lt;P&gt;Hello! I want to ask a question please!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Referring to Spot VMs with the "Cost Optimized" setting:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the case of Endpoint X-Small, which are 2 workers, if I send 10 simultaneous queries and a worker is evicted, can I have an error in any of these queries? or just would I just have to wait for another worker to come up and then I would have a slow execution?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My fear is that there may be an error when a worker is evicted due to what the tip below says that if a spot instance is retrieved, queries running on that instance will need to be resubmitted&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="image"&gt;&lt;img src="https://community.databricks.com/t5/image/serverpage/image-id/2076iEF947882110AFD9C/image-size/large?v=v2&amp;amp;px=999" role="button" title="image" alt="image" /&gt;&lt;/span&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Unfortunately I am unable to test this...so I came to try this information here on the forum&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 14:36:51 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28300#M20123</guid>
      <dc:creator>Gvsmao</dc:creator>
      <dc:date>2022-02-14T14:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Databricks - Spot VMs (Cost Optimized)</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28302#M20125</link>
      <description>&lt;P&gt;I think with spot instances there is always the chance of getting errors because of eviction.&lt;/P&gt;&lt;P&gt;If all workers are evicted the query state is probably also lost, unless Databricks SQL keeps this stored somewhere.&lt;/P&gt;&lt;P&gt;For job clusters that is the case anyway, perhaps it works different on databricks sql.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 15:31:33 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28302#M20125</guid>
      <dc:creator>-werners-</dc:creator>
      <dc:date>2022-02-14T15:31:33Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Databricks - Spot VMs (Cost Optimized)</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28303#M20126</link>
      <description>&lt;P&gt;Okay, thanks for the contribution @Werner Stinckens​&amp;nbsp;!&lt;/P&gt;&lt;P&gt;That's the point really, does Databricks SQL keep it stored somehow so that there are no errors on the worker's return?&lt;/P&gt;&lt;P&gt;I will have to really test.&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 16:50:25 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28303#M20126</guid>
      <dc:creator>Gvsmao</dc:creator>
      <dc:date>2022-02-14T16:50:25Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Databricks - Spot VMs (Cost Optimized)</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28304#M20127</link>
      <description>&lt;P&gt;@Gvsmao .​&amp;nbsp;- Hello there! My name is Piper, and I'm a moderator for Databricks. When you find your answer, would you come back to let us know and mark your answer as best, unless werner's answer helped the most? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Either way, we are interested!&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 18:15:38 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28304#M20127</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-02-14T18:15:38Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Databricks - Spot VMs (Cost Optimized)</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28305#M20128</link>
      <description>&lt;P&gt;@Piper Wilson​&amp;nbsp; Ok!&lt;/P&gt;</description>
      <pubDate>Mon, 14 Feb 2022 20:00:22 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28305#M20128</guid>
      <dc:creator>Gvsmao</dc:creator>
      <dc:date>2022-02-14T20:00:22Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Databricks - Spot VMs (Cost Optimized)</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28306#M20129</link>
      <description>&lt;P&gt;I doubt that will be the case. It would mean databricks has to run some kind of permanent node that contains the query state in ram (or on disk).&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 07:04:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28306#M20129</guid>
      <dc:creator>-werners-</dc:creator>
      <dc:date>2022-02-15T07:04:11Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Databricks - Spot VMs (Cost Optimized)</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28307#M20130</link>
      <description>&lt;P&gt;I agree with you&lt;/P&gt;</description>
      <pubDate>Tue, 15 Feb 2022 12:36:04 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28307#M20130</guid>
      <dc:creator>Gvsmao</dc:creator>
      <dc:date>2022-02-15T12:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Databricks - Spot VMs (Cost Optimized)</title>
      <link>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28308#M20131</link>
      <description>&lt;P&gt;Thanks for the information, I will try to figure it out for more. Keep sharing such informative post.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://www.mygroundbiz.org/" alt="https://www.mygroundbiz.org/" target="_blank"&gt;www.mygroundbiz.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 26 Mar 2022 10:26:46 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/sql-databricks-spot-vms-cost-optimized/m-p/28308#M20131</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-03-26T10:26:46Z</dc:date>
    </item>
  </channel>
</rss>

