If you create an environment with 2 scheduler nodes & 2 consumer nodes. The first scheduler node is acting as central node, the second as fail-over node. The only active proxy service is running on the first scheduler node... so the URL to browse to the hub is something like http://firstschedulernode/hub
What happens when the failover takes over? This URL will no longer be available? ... so endusers can't access the environment anymore. Am I missing something or can someone give me some insights/best-practices in how this works?
Yes you're right, since the URL is the direct URL of the first scheduler node, this address reach directly the first scheduler.
In case this server is no down, users has to use the second scheduler node.
If you want a more user friendly solution, here is some leads:
Create a generic address with a DNS redirection. Default redirection points on the first scheduler node and once this node is down, you have to manually change the redirection to the second. this solution is simple to handle, but require manual step to switch to the other scheduler node (maybe an automated solution exists, but I'm not sure of that).
The best solution is to have a Load Balancing solution on top of Qlik (eg. F5 Load Balancer). This solution is fully automated, but require another software on top of Qlik Sense.
