<?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 Additional Hard Drive for Flowfile Repository in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Additional-Hard-Drive-for-Flowfile-Repository/m-p/207653#M84077</link>
    <description>&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a Nifi cluster on production and realized I need additional disk space for flowfile repository. What would be the best way to handle the scenario? If I mount a new disk from Ambari using the following configuration:&lt;/P&gt;&lt;PRE&gt;nifi.flowfile.repository.directory.flowfile2&lt;/PRE&gt;&lt;P&gt;would it be smart enough to load balance between existing drive and the new drive? Would it only apply to new incoming flowfiles?&lt;/P&gt;</description>
    <pubDate>Sat, 06 Oct 2018 07:24:54 GMT</pubDate>
    <dc:creator>daniel_ahn</dc:creator>
    <dc:date>2018-10-06T07:24:54Z</dc:date>
    <item>
      <title>Additional Hard Drive for Flowfile Repository</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Additional-Hard-Drive-for-Flowfile-Repository/m-p/207653#M84077</link>
      <description>&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a Nifi cluster on production and realized I need additional disk space for flowfile repository. What would be the best way to handle the scenario? If I mount a new disk from Ambari using the following configuration:&lt;/P&gt;&lt;PRE&gt;nifi.flowfile.repository.directory.flowfile2&lt;/PRE&gt;&lt;P&gt;would it be smart enough to load balance between existing drive and the new drive? Would it only apply to new incoming flowfiles?&lt;/P&gt;</description>
      <pubDate>Sat, 06 Oct 2018 07:24:54 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Additional-Hard-Drive-for-Flowfile-Repository/m-p/207653#M84077</guid>
      <dc:creator>daniel_ahn</dc:creator>
      <dc:date>2018-10-06T07:24:54Z</dc:date>
    </item>
    <item>
      <title>Re: Additional Hard Drive for Flowfile Repository</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Additional-Hard-Drive-for-Flowfile-Repository/m-p/207654#M84078</link>
      <description>&lt;A rel="user" href="https://community.cloudera.com/users/97402/danielahn.html" nodeid="97402"&gt;@Daniel Ahn&lt;/A&gt;&lt;P&gt;NiFi does not support multiple FlowFile repositories.  Only the Content and Provenance repositories support multiple locations (these are the only two repositories that may get very large).&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;It is highly recommended that the FlowFile repository is however located on its own separate disk or when that is not possible on its own separate logical volume.&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;You can move the existing FlowFile repository to a new disk.  &lt;/P&gt;&lt;P&gt;1. Add a new disk to your NiFi server (or create a new logical volume)&lt;BR /&gt;2. Stop NiFi&lt;BR /&gt;3. Move entire contents from original flowfile_repository directory to new flowfile_repository location.&lt;BR /&gt;4. Verify proper ownership/permissions of all moved files&lt;BR /&gt;5. Edit nifi.properties so that "nifi.flowfile.repository.directory=" now points to new location.&lt;BR /&gt;6. Start NiFi&lt;/P&gt;&lt;P&gt;-&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Matt&lt;BR /&gt;-&lt;BR /&gt;If you found this answer addressed your question, please take a moment to login in and click the "ACCEPT" link.&lt;/P&gt;</description>
      <pubDate>Mon, 08 Oct 2018 19:35:39 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Additional-Hard-Drive-for-Flowfile-Repository/m-p/207654#M84078</guid>
      <dc:creator>MattWho</dc:creator>
      <dc:date>2018-10-08T19:35:39Z</dc:date>
    </item>
  </channel>
</rss>

