<?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 Distributed Map Cache Persisting in Support Questions</title>
    <link>https://community.cloudera.com/t5/Support-Questions/NiFi-Distributed-Map-Cache-Persisting/m-p/371924#M241115</link>
    <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/79092"&gt;@drewski7&lt;/a&gt;&amp;nbsp; &amp;nbsp;I think the solution you are looking for is to use one of the alternative data stores that lives outside of NiFi with the map cache.&amp;nbsp; The options are Redis, Hbase, Cassandra, Couchbase:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Screen Shot 2023-06-01 at 9.30.28 AM.png" style="width: 400px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/37705i3745DA225B9B24EB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screen Shot 2023-06-01 at 9.30.28 AM.png" alt="Screen Shot 2023-06-01 at 9.30.28 AM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They will give you greater control and they are preferred for production and large volumes.&lt;/P&gt;</description>
    <pubDate>Thu, 01 Jun 2023 13:31:35 GMT</pubDate>
    <dc:creator>steven-matison</dc:creator>
    <dc:date>2023-06-01T13:31:35Z</dc:date>
    <item>
      <title>NiFi Distributed Map Cache Persisting</title>
      <link>https://community.cloudera.com/t5/Support-Questions/NiFi-Distributed-Map-Cache-Persisting/m-p/371880#M241107</link>
      <description>&lt;P&gt;I have a multinode NiFi Cluster running in Docker Containers and I configured the DistributeMapCacheClient and DistributedMapCacheServer to point to a particular container's hostname and set the persistence directory property such that each node in the cluster uses the same Map Cache.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I want to make that the MapCache persists even after I restart the container or create a new container. How would I configure that to happen?&lt;/P&gt;</description>
      <pubDate>Wed, 31 May 2023 22:09:59 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/NiFi-Distributed-Map-Cache-Persisting/m-p/371880#M241107</guid>
      <dc:creator>drewski7</dc:creator>
      <dc:date>2023-05-31T22:09:59Z</dc:date>
    </item>
    <item>
      <title>Re: NiFi Distributed Map Cache Persisting</title>
      <link>https://community.cloudera.com/t5/Support-Questions/NiFi-Distributed-Map-Cache-Persisting/m-p/371924#M241115</link>
      <description>&lt;P&gt;&lt;a href="https://community.cloudera.com/t5/user/viewprofilepage/user-id/79092"&gt;@drewski7&lt;/a&gt;&amp;nbsp; &amp;nbsp;I think the solution you are looking for is to use one of the alternative data stores that lives outside of NiFi with the map cache.&amp;nbsp; The options are Redis, Hbase, Cassandra, Couchbase:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-center" image-alt="Screen Shot 2023-06-01 at 9.30.28 AM.png" style="width: 400px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/37705i3745DA225B9B24EB/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screen Shot 2023-06-01 at 9.30.28 AM.png" alt="Screen Shot 2023-06-01 at 9.30.28 AM.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They will give you greater control and they are preferred for production and large volumes.&lt;/P&gt;</description>
      <pubDate>Thu, 01 Jun 2023 13:31:35 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Support-Questions/NiFi-Distributed-Map-Cache-Persisting/m-p/371924#M241115</guid>
      <dc:creator>steven-matison</dc:creator>
      <dc:date>2023-06-01T13:31:35Z</dc:date>
    </item>
  </channel>
</rss>

