Qlik Community

Qlik Sense Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

brantley_hobbs
New Contributor III

How can I get the scheduler to run a task on a particular node?

Hi all!

I have what I believe is probably a common scenario, but I simply can't figure out how to configure Qlik in this case.  I need to ensure that some reload tasks run on a particular rim node.  The rim node in question is the only one that has the correct firewall access to the underlying database servers that a particular app needs.

I found that when the scheduler is set up as a slave, the master node (Central) just randomly distributes reloads to any given node running the scheduler.

How can I guarantee that a particular reload task runs on a particular node?  The documentation wasn't very clear about the distinction between Master/Slave/Master&Slave.

Thanks!

Tags (2)
3 Replies
jaisoni_trp
Contributor II

Re: How can I get the scheduler to run a task on a particular node?

I guess we have this functionally in latest QlikView version 12.10 but still not available in Qlik Sense. I am also looking to cluster the RIM nodes and segregating heavy duty tasks on a dedicated node.

riccardozenere
Contributor III

Re: How can I get the scheduler to run a task on a particular node?

I was totally looking for this feature.

Isn't there neither some kind of rule that can force it?

brantley_hobbs
New Contributor III

Re: How can I get the scheduler to run a task on a particular node?

I had an idea that I might be able to make a QRS API call to reload the task on a particular rim node (using the excellent Qlik-Cli Powershell plugin), but when I list apps with Get-QlikApp -full, I get zero results.  I know the connection is being made because I can do Get-QlikAbout and get back information from the API.

Funny thing is that if I do a reload on an app that I *know* is not synchronized to that rim node, it succeeds, which tells me that it does not matter which QRS proxy you call the command on, the actual execution still occurs on the central node.

Can anyone confirm this?

Community Browser