<?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>article Qlik Sense Failover Central node: Requirements and Considerations in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Failover-Central-node-Requirements-and-Considerations/ta-p/1713240</link>
    <description>&lt;P&gt;When adding additional nodes to your multi node setup, each new node can be configured to act as a failover candidate. This node will then regularly check to verify that the primary central node is active, and if it does not receive a response within 10 minutes, the failover candidate will become the active central node.&lt;/P&gt;
&lt;P&gt;For a node to be a failover candidate, it must run the following services:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN class="CommonComponentsQRSName"&gt;Qlik Sense Repository Service&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="CommonComponentsQESName"&gt;Qlik Sense Engine Service&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="CommonComponentsQPSName"&gt;Qlik Sense Proxy Service&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="CommonComponentsQSSName"&gt;Qlik Sense Scheduler Service&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;To enable the feature in the Qlik Sense Management Console:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;While adding a new node, locate &lt;STRONG&gt;Node Configuration&amp;nbsp;&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Check &lt;STRONG&gt;Failover candidate&amp;nbsp;&lt;/STRONG&gt;adding the node (see fig 1)&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="fig 1" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/90954iCEA0161C899A527A/image-size/large?v=v2&amp;amp;px=999" role="button" title="adding a new node.png" alt="fig 1" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;fig 1&lt;/span&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;To change this setting&amp;nbsp;&lt;EM&gt;after&amp;nbsp;&lt;/EM&gt;having added the rim node, see&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Elevating-an-existing-Qlik-Sense-rim-node-to-a-Failover/ta-p/1990733" target="_blank" rel="noopener"&gt;Elevating an existing Qlik Sense rim node to a Failover Candidate&lt;/A&gt;.&lt;/LI&gt;
&lt;/OL&gt;
&lt;H4&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Requirements and considerations:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;In order for a node to act as a failover candidate, the respective setting "Failover candidate" needs to be activated under the Node's configuration, and the engine, repository, proxy, and scheduler services must be active.&lt;/LI&gt;
&lt;LI&gt;If the failover candidate becomes the active central node, it will also automatically become the manager scheduler.&lt;/LI&gt;
&lt;LI&gt;Because the scheduler service must be active, the failover candidate will function as a worker scheduler and will receive reload jobs. If it is necessary to minimize the number of reload jobs this node performs, you can set the Max concurrent reloads to 1.&amp;nbsp; If this method is used the&amp;nbsp;customer is responsible for setting this and if it breaks your failover it is the customers responsibility to find root cause. By modifying failover this could cause the failover to not perform as defined. Failover is there to backup your central node in case of failure.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Clients wishing to use this feature must &lt;STRONG&gt;deploy a dedicated server to host the PostgreSQL database&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI&gt;Once a node is selected as a failover candidate, this setting cannot be disabled.&lt;/LI&gt;
&lt;LI&gt;By default, the failover timeout is set to 10 minutes, and this setting cannot be changed in the QMC. To change the setting, you can use Qlik-CLI and the Update-QlikServiceCluster cmdlet. For details, see&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/Change-Central-Node-Failover-Timeout/ta-p/1716586" target="_blank" rel="noopener"&gt;Change Central Node Failover Timeout&lt;/A&gt;&amp;nbsp;article.&lt;/LI&gt;
&lt;LI&gt;The Nodes section of the QMC identifies which node is currently the central node and indicates which nodes are designated as failover candidates. However, to view this information you must access the&amp;nbsp;&lt;STRONG&gt;Column selector&lt;/STRONG&gt;&amp;nbsp;and check&amp;nbsp;&lt;STRONG&gt;Central node&lt;/STRONG&gt;&amp;nbsp;and&amp;nbsp;&lt;STRONG&gt;Failover candidate&lt;/STRONG&gt;, as these columns are not enabled by default. For details, see&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/sense/February2018/Subsystems/ManagementConsole/Content/nodes-overview.htm" target="_blank" rel="noopener"&gt;Nodes&lt;/A&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Video demonstration&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;This video was recorded for Qlik Sense 2017. The instructions are still valid in current versions.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;div class="video-embed-center video-embed"&gt;&lt;iframe class="embedly-embed" src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FY5IblMGwrLU%3Ffeature%3Doembed&amp;amp;display_name=YouTube&amp;amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DY5IblMGwrLU&amp;amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FY5IblMGwrLU%2Fhqdefault.jpg&amp;amp;type=text%2Fhtml&amp;amp;schema=youtube" width="200" height="112" scrolling="no" title="STT - Failover in Qlik Sense - Practical Guide and Implications" frameborder="0" allow="autoplay; fullscreen; encrypted-media; picture-in-picture" allowfullscreen="true"&gt;&lt;/iframe&gt;&lt;/div&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Related content:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;DIV style="margin-left: 40px;"&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Manually-Failover-the-Central-Node/ta-p/1714995" target="_self"&gt;Manually Failover the Central Node&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Elevating-an-existing-Qlik-Sense-rim-node-to-a-Failover/ta-p/1990733" target="_blank" rel="noopener"&gt;Elevating an existing Qlik Sense rim node to a Failover Candidate&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/Configuring-PostgreSQL-Failover-and-Redundancy-for-Qlik-Sense/ta-p/1768951" target="_blank" rel="noopener"&gt;Configuring PostgreSQL Failover and Redundancy June 2018&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://help.qlik.com/en-US/sense-admin/November2020/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Failover.htm" target="_self" rel="nofollow noreferrer noreferrer"&gt;Configuring failover for central node resiliency&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/Change-Central-Node-Failover-Timeout/ta-p/1716586" target="_blank" rel="noopener"&gt;Change Central Node Failover Timeout&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="margin-left: 40px;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV style="margin-left: 40px;"&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
    <pubDate>Mon, 10 Oct 2022 11:11:50 GMT</pubDate>
    <dc:creator>Sonja_Bauernfeind</dc:creator>
    <dc:date>2022-10-10T11:11:50Z</dc:date>
    <item>
      <title>Qlik Sense Failover Central node: Requirements and Considerations</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Failover-Central-node-Requirements-and-Considerations/ta-p/1713240</link>
      <description>&lt;P&gt;When adding additional nodes to your multi node setup, each new node can be configured to act as a failover candidate. This node will then regularly check to verify that the primary central node is active, and if it does not receive a response within 10 minutes, the failover candidate will become the active central node.&lt;/P&gt;
&lt;P&gt;For a node to be a failover candidate, it must run the following services:&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;SPAN class="CommonComponentsQRSName"&gt;Qlik Sense Repository Service&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="CommonComponentsQESName"&gt;Qlik Sense Engine Service&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="CommonComponentsQPSName"&gt;Qlik Sense Proxy Service&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI&gt;&lt;SPAN class="CommonComponentsQSSName"&gt;Qlik Sense Scheduler Service&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;To enable the feature in the Qlik Sense Management Console:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;While adding a new node, locate &lt;STRONG&gt;Node Configuration&amp;nbsp;&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Check &lt;STRONG&gt;Failover candidate&amp;nbsp;&lt;/STRONG&gt;adding the node (see fig 1)&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="fig 1" style="width: 999px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/90954iCEA0161C899A527A/image-size/large?v=v2&amp;amp;px=999" role="button" title="adding a new node.png" alt="fig 1" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;fig 1&lt;/span&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;To change this setting&amp;nbsp;&lt;EM&gt;after&amp;nbsp;&lt;/EM&gt;having added the rim node, see&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Elevating-an-existing-Qlik-Sense-rim-node-to-a-Failover/ta-p/1990733" target="_blank" rel="noopener"&gt;Elevating an existing Qlik Sense rim node to a Failover Candidate&lt;/A&gt;.&lt;/LI&gt;
&lt;/OL&gt;
&lt;H4&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;LI-PRODUCT title="Qlik Sense Enterprise on Windows" id="qlikSenseEnterpriseWindows"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Requirements and considerations:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;In order for a node to act as a failover candidate, the respective setting "Failover candidate" needs to be activated under the Node's configuration, and the engine, repository, proxy, and scheduler services must be active.&lt;/LI&gt;
&lt;LI&gt;If the failover candidate becomes the active central node, it will also automatically become the manager scheduler.&lt;/LI&gt;
&lt;LI&gt;Because the scheduler service must be active, the failover candidate will function as a worker scheduler and will receive reload jobs. If it is necessary to minimize the number of reload jobs this node performs, you can set the Max concurrent reloads to 1.&amp;nbsp; If this method is used the&amp;nbsp;customer is responsible for setting this and if it breaks your failover it is the customers responsibility to find root cause. By modifying failover this could cause the failover to not perform as defined. Failover is there to backup your central node in case of failure.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;Clients wishing to use this feature must &lt;STRONG&gt;deploy a dedicated server to host the PostgreSQL database&lt;/STRONG&gt;.&lt;/LI&gt;
&lt;LI&gt;Once a node is selected as a failover candidate, this setting cannot be disabled.&lt;/LI&gt;
&lt;LI&gt;By default, the failover timeout is set to 10 minutes, and this setting cannot be changed in the QMC. To change the setting, you can use Qlik-CLI and the Update-QlikServiceCluster cmdlet. For details, see&amp;nbsp;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/Change-Central-Node-Failover-Timeout/ta-p/1716586" target="_blank" rel="noopener"&gt;Change Central Node Failover Timeout&lt;/A&gt;&amp;nbsp;article.&lt;/LI&gt;
&lt;LI&gt;The Nodes section of the QMC identifies which node is currently the central node and indicates which nodes are designated as failover candidates. However, to view this information you must access the&amp;nbsp;&lt;STRONG&gt;Column selector&lt;/STRONG&gt;&amp;nbsp;and check&amp;nbsp;&lt;STRONG&gt;Central node&lt;/STRONG&gt;&amp;nbsp;and&amp;nbsp;&lt;STRONG&gt;Failover candidate&lt;/STRONG&gt;, as these columns are not enabled by default. For details, see&amp;nbsp;&lt;A href="https://help.qlik.com/en-US/sense/February2018/Subsystems/ManagementConsole/Content/nodes-overview.htm" target="_blank" rel="noopener"&gt;Nodes&lt;/A&gt;.&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Video demonstration&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;This video was recorded for Qlik Sense 2017. The instructions are still valid in current versions.&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;div class="video-embed-center video-embed"&gt;&lt;iframe class="embedly-embed" src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FY5IblMGwrLU%3Ffeature%3Doembed&amp;amp;display_name=YouTube&amp;amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DY5IblMGwrLU&amp;amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FY5IblMGwrLU%2Fhqdefault.jpg&amp;amp;type=text%2Fhtml&amp;amp;schema=youtube" width="200" height="112" scrolling="no" title="STT - Failover in Qlik Sense - Practical Guide and Implications" frameborder="0" allow="autoplay; fullscreen; encrypted-media; picture-in-picture" allowfullscreen="true"&gt;&lt;/iframe&gt;&lt;/div&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Related content:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;DIV style="margin-left: 40px;"&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Manually-Failover-the-Central-Node/ta-p/1714995" target="_self"&gt;Manually Failover the Central Node&lt;/A&gt;&amp;nbsp;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Official-Support-Articles/Elevating-an-existing-Qlik-Sense-rim-node-to-a-Failover/ta-p/1990733" target="_blank" rel="noopener"&gt;Elevating an existing Qlik Sense rim node to a Failover Candidate&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/Configuring-PostgreSQL-Failover-and-Redundancy-for-Qlik-Sense/ta-p/1768951" target="_blank" rel="noopener"&gt;Configuring PostgreSQL Failover and Redundancy June 2018&lt;/A&gt;&lt;BR /&gt;&lt;A href="https://help.qlik.com/en-US/sense-admin/November2020/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Failover.htm" target="_self" rel="nofollow noreferrer noreferrer"&gt;Configuring failover for central node resiliency&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Support-Knowledge-Base/Change-Central-Node-Failover-Timeout/ta-p/1716586" target="_blank" rel="noopener"&gt;Change Central Node Failover Timeout&lt;/A&gt;&lt;/DIV&gt;
&lt;DIV style="margin-left: 40px;"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV style="margin-left: 40px;"&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Mon, 10 Oct 2022 11:11:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Failover-Central-node-Requirements-and-Considerations/ta-p/1713240</guid>
      <dc:creator>Sonja_Bauernfeind</dc:creator>
      <dc:date>2022-10-10T11:11:50Z</dc:date>
    </item>
  </channel>
</rss>

