<?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>question time to provision a spark cluster in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/time-to-provision-a-spark-cluster/m-p/148146#M28341</link>
    <description>&lt;P&gt;setting up a 15 node cluster; if required consider 3 master nodes and 12 data nodes. setting up HDFS-YARN-SPARK; considering hardware is available and setup with Suse Linux -- how much time should a Project Mgr allocate to provision a production worthy cluster using Blueprints?&lt;/P&gt;</description>
    <pubDate>Fri, 16 Sep 2022 10:19:29 GMT</pubDate>
    <dc:creator>asim_munshi</dc:creator>
    <dc:date>2022-09-16T10:19:29Z</dc:date>
    <item>
      <title>time to provision a spark cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/time-to-provision-a-spark-cluster/m-p/148146#M28341</link>
      <description>&lt;P&gt;setting up a 15 node cluster; if required consider 3 master nodes and 12 data nodes. setting up HDFS-YARN-SPARK; considering hardware is available and setup with Suse Linux -- how much time should a Project Mgr allocate to provision a production worthy cluster using Blueprints?&lt;/P&gt;</description>
      <pubDate>Fri, 16 Sep 2022 10:19:29 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/time-to-provision-a-spark-cluster/m-p/148146#M28341</guid>
      <dc:creator>asim_munshi</dc:creator>
      <dc:date>2022-09-16T10:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: time to provision a spark cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/time-to-provision-a-spark-cluster/m-p/148147#M28342</link>
      <description>&lt;P&gt;Hi &lt;A rel="user" href="https://community.cloudera.com/users/10465/asim-munshi.html" nodeid="10465"&gt;@Asim munshi&lt;/A&gt;. This really depends on a lot of variables.&lt;/P&gt;&lt;P&gt;Is this the first time that the team is doing this? Assuming they're using Ambari, that they're exprienced in this and have done it before in several other different environments, but they're also looking to perform performance and stability testing before handover etc I would recommend 1 week which includes at least a day and a half of contingency for things that crop up during deployment.&lt;/P&gt;&lt;P&gt;If however this environment has been used before i.e. networking, firewalling, routing, etc etc is all in a known good state, and the hardware is all 100% correctly provisioned you could easily get everything done including Ambari and the whole cluster in a morning.&lt;/P&gt;&lt;P&gt;I realise that's quite a wide range of times but hopefully that gives you some kind of range to work with.&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;</description>
      <pubDate>Mon, 16 May 2016 15:32:14 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/time-to-provision-a-spark-cluster/m-p/148147#M28342</guid>
      <dc:creator>drussell</dc:creator>
      <dc:date>2016-05-16T15:32:14Z</dc:date>
    </item>
    <item>
      <title>Re: time to provision a spark cluster</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/time-to-provision-a-spark-cluster/m-p/148148#M28343</link>
      <description>&lt;P&gt;thanks &lt;A rel="user" href="https://community.cloudera.com/users/136/drussell.html" nodeid="136"&gt;@drussell&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 17 May 2016 07:57:20 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/time-to-provision-a-spark-cluster/m-p/148148#M28343</guid>
      <dc:creator>asim_munshi</dc:creator>
      <dc:date>2016-05-17T07:57:20Z</dc:date>
    </item>
  </channel>
</rss>

