<?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 Spot label in pool even though the configuration selected is all on-demand in Get Started Discussions</title>
    <link>https://community.databricks.com/t5/get-started-discussions/spot-label-in-pool-even-though-the-configuration-selected-is-all/m-p/75343#M7553</link>
    <description>&lt;P&gt;Why is there a spot label in pool even though the configuration selected is all on-demand? can someone explain?&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jun 2024 12:10:01 GMT</pubDate>
    <dc:creator>hkadhao</dc:creator>
    <dc:date>2024-06-21T12:10:01Z</dc:date>
    <item>
      <title>Spot label in pool even though the configuration selected is all on-demand</title>
      <link>https://community.databricks.com/t5/get-started-discussions/spot-label-in-pool-even-though-the-configuration-selected-is-all/m-p/75343#M7553</link>
      <description>&lt;P&gt;Why is there a spot label in pool even though the configuration selected is all on-demand? can someone explain?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 12:10:01 GMT</pubDate>
      <guid>https://community.databricks.com/t5/get-started-discussions/spot-label-in-pool-even-though-the-configuration-selected-is-all/m-p/75343#M7553</guid>
      <dc:creator>hkadhao</dc:creator>
      <dc:date>2024-06-21T12:10:01Z</dc:date>
    </item>
  </channel>
</rss>

