STT - Failover in Qlik Sense - Practical Guide and Implications

    In this webinar we will discuss:

    • The concept of a floating Central node
    • How to failover / failback in a graceful way
    • Live Demonstration
    • Troubleshooting Tips

    For best viewing, we recommend you set the highest video resolution


    Q&A - Failover in Qlik Sense

     

    Q: Why would an administrator want to utilize fail-over?

    A: To allow resiliency in the environment. The obvious use of this is if the Repository database and Apps are hosted off the Central node.

     

    Q: What build is fail-over introduced?

    A: Fail-over was introduced in the June 2017 release.

     

    Q: Is the fail-over automatic or API driven?

    A: Both are possible. By default, it fails over after 10 minutes (http://help.qlik.com/en-US/sense/June2017/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Failover.htm). Or earlier based on API calls.

     

    Q: Can you fail-over if the Central node hosts the Repository Database and the apps?

    A: Yes, but there's little added value to this style of deployment.

     

    Q: Do you have to add a new node to allow the node to be a fail-over candidate?

    A: Out of the box, yes. If you're comfortable with APIs then you can elevate an existing RIM node. See article Elevating an existing RIM node to fail-over candidate in June 2017 or higher in our knowledge base.