Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I have been doing some studying on performance tuning and Scheduling Service. Here is the scenario:
A. Consumer Node is slow, has a ton of apps to reload.
B. The consumer node runs the Engine, Scheduler, Repository, and Proxy services.
C. The scheduler node runs the Engine, Scheduler, and Repository services.
The suggested fix in this situation was to change the Scheduler Node to 'Master'.
My question from this is how does Qlik Sense 'Master' Schedule Service decide where to put the reload tasks. What are the criteria, how are they weighted?
Thanks Community!
Hi,
It is all about round robin algorithm. Even I want to understand how and on what basis Qlik does that.
Check below thread
https://community.qlik.com/t5/Knowledge/Load-Balancing-in-Qlik-Sense/ta-p/1715174
Qlik follows round robin algorithm. Whichever Slave or non master server is best available, task executes there. If your scheduler server is master or central server and you make it Master only then your reloads will have no place to happen. If you have different central server than scheduler server then make Master and Slave both to central and slave to scheduler so your load will be distributed.
If a post helps to resolve your issue, please mark the appropriate replies as "Accept as Solution" or Like it.
Reach out to me at kumar.rohit1609@gmail.com if there is need of any clarification or assistance
Connect with me on LinkedIn https://www.linkedin.com/in/rohit-kumar-67ba152b/
To get latest updates and articles, join Qlik community at https://www.facebook.com/QlikIntellectuals
Best,
Rohit
Hi,
It is all about round robin algorithm. Even I want to understand how and on what basis Qlik does that.
Check below thread
https://community.qlik.com/t5/Knowledge/Load-Balancing-in-Qlik-Sense/ta-p/1715174
Hello @AshutoshBhumaker,
Thank you for the reply. In a 'Master' and 'Slave' scheduler, the Master 'decides' where the Task should go. It must be outside of the regular load balancing routine. I agree the load balancing is round robin. Would you be able to confirm the Master and Slave Scheduler also only use round robin?
I think it is round robin if you do not configure 'Master and 'Slave' for instance, but not after...
Thank you again for the reply, and thank you in advance for any additional clarification.
Qlik follows round robin algorithm. Whichever Slave or non master server is best available, task executes there. If your scheduler server is master or central server and you make it Master only then your reloads will have no place to happen. If you have different central server than scheduler server then make Master and Slave both to central and slave to scheduler so your load will be distributed.
If a post helps to resolve your issue, please mark the appropriate replies as "Accept as Solution" or Like it.
Reach out to me at kumar.rohit1609@gmail.com if there is need of any clarification or assistance
Connect with me on LinkedIn https://www.linkedin.com/in/rohit-kumar-67ba152b/
To get latest updates and articles, join Qlik community at https://www.facebook.com/QlikIntellectuals
Best,
Rohit