Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.
We are getting an error in the QMC when scheduled tasks are starting to queue up (waiting on what is executing to begin). My timeout is set to 120 minutes, but these are immediately failing with the error above (No slave scheduler found).
We have a single scheduler node configured as Master and Slave, and the engine service is running on this node. Confirmed QMC shows the service is running (and so does Windows). Resources on the machine are not maxed out. I am setup to allow 6 concurrent tasks to run (based on 8 cores). It seems like as soon as several tasks start to get in the triggered or queued status this happens.
Does anyone have any thoughts on how to troubleshoot?
tbh it should be marked as critical issue and solved as soon as possible. yet, Qlik is "investigating" for past 6months.. it basically disables scheduler functionality. entirely
I understand the frustration.
Unfortunately this issue happens only in a very limited number of environments, and we have not been able to reproduce it in any of our labs, which would have sped up resolution.
For this reason we ask everyone to log a case with Support, either directly or indirectly, to gather as much information and putting weight behind the investigation.
In the meantime, R&D is also working on alternatives to solve this.
You mentioned having had problems with Qlik Support: can you please mention some case numbers or your account/license (even with a private message, of course), so that I can have a look and understand what the issue was? Thanks for the understanding!
Is this something that can be typically resolved by an upgrade? I've seen a few scenarios of this happening recently on April and June 2018 installations, and the random nature of it can cause some major issues when dealing with complex task chains.
Hi @brian_booden and everyone else.
There has been some improvements along the way, but the bug has been fully fixed in the code just recently.
The release of the fix is currently planned for June 2019: https://support.qlik.com/articles/000053947
Thanks for the patience and understanding!
Thanks for the patience, everyone!
We have fixes finally coming or already out in patches for versions from September 2018 and forward.
More details about the patch versions in our support article.