<?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 Failover Heartbeat in Search the Community</title>
    <link>https://community.qlik.com/t5/Search-the-Community/Failover-Heartbeat/m-p/1826334#M460</link>
    <description>&lt;P&gt;Failover Heartbeat:&amp;nbsp; Is there documentation that shows how the failover process works between nodes and the repository, and over which ports/protocols. This will help us monitor events within the system in the future and help us explore root causes down the line, however without understanding the end to end process, it will be difficult to do (e.g. does the rim communicate directly to the CN, or do they both update the heartbeat table in postgres every xx seconds … etc.).&lt;/P&gt;</description>
    <pubDate>Tue, 03 Aug 2021 12:50:03 GMT</pubDate>
    <dc:creator>TH1</dc:creator>
    <dc:date>2021-08-03T12:50:03Z</dc:date>
    <item>
      <title>Failover Heartbeat</title>
      <link>https://community.qlik.com/t5/Search-the-Community/Failover-Heartbeat/m-p/1826334#M460</link>
      <description>&lt;P&gt;Failover Heartbeat:&amp;nbsp; Is there documentation that shows how the failover process works between nodes and the repository, and over which ports/protocols. This will help us monitor events within the system in the future and help us explore root causes down the line, however without understanding the end to end process, it will be difficult to do (e.g. does the rim communicate directly to the CN, or do they both update the heartbeat table in postgres every xx seconds … etc.).&lt;/P&gt;</description>
      <pubDate>Tue, 03 Aug 2021 12:50:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Search-the-Community/Failover-Heartbeat/m-p/1826334#M460</guid>
      <dc:creator>TH1</dc:creator>
      <dc:date>2021-08-03T12:50:03Z</dc:date>
    </item>
  </channel>
</rss>

