<?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 Re: Nifi with Isilon? in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159399#M21048</link>
    <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/137/sdutta.html" nodeid="137"&gt;@Shivaji&lt;/A&gt;  &lt;/P&gt;</description>
    <pubDate>Fri, 26 Feb 2016 11:11:13 GMT</pubDate>
    <dc:creator>aervits</dc:creator>
    <dc:date>2016-02-26T11:11:13Z</dc:date>
    <item>
      <title>Nifi with Isilon?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159398#M21047</link>
      <description>&lt;P&gt;Would it ever make sense to put any of the NiFi Cluster repositories (Flow File, Content, Provenance) in a NAS like Isilon?  I know disk can be the bottleneck but you also want these repositories on drives with a strong RAID, thus my question.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Feb 2016 11:09:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159398#M21047</guid>
      <dc:creator>ccasano</dc:creator>
      <dc:date>2016-02-26T11:09:57Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi with Isilon?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159399#M21048</link>
      <description>&lt;P&gt;&lt;A rel="user" href="https://community.cloudera.com/users/137/sdutta.html" nodeid="137"&gt;@Shivaji&lt;/A&gt;  &lt;/P&gt;</description>
      <pubDate>Fri, 26 Feb 2016 11:11:13 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159399#M21048</guid>
      <dc:creator>aervits</dc:creator>
      <dc:date>2016-02-26T11:11:13Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi with Isilon?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159400#M21049</link>
      <description>&lt;P&gt;I haven't tested this myself but NAS/SAN arrangements have worked quite well in the past.  Needs testing to understand latencies/tradeoffs but frankly I suspect it will work just fine.&lt;/P&gt;</description>
      <pubDate>Fri, 26 Feb 2016 11:11:16 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159400#M21049</guid>
      <dc:creator>JoeWitt</dc:creator>
      <dc:date>2016-02-26T11:11:16Z</dc:date>
    </item>
    <item>
      <title>Re: Nifi with Isilon?</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159401#M21050</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/299/ccasano.html" nodeid="299" target="_blank"&gt;@ccasano&lt;/A&gt;&lt;P&gt;I don't see any issues in having Isilon to store the workflow repositories. Isilon is scalable storage solution and based on my experience, Isilon can be a good solution based on &lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="2426-screen-shot-2016-02-26-at-95810-am.png" style="width: 1428px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/20768i373ED0FE854B1FE1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="2426-screen-shot-2016-02-26-at-95810-am.png" alt="2426-screen-shot-2016-02-26-at-95810-am.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 18 Aug 2019 12:04:56 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Nifi-with-Isilon/m-p/159401#M21050</guid>
      <dc:creator>nsabharwal</dc:creator>
      <dc:date>2019-08-18T12:04:56Z</dc:date>
    </item>
  </channel>
</rss>

