Scheduler problem

[YoussefBelloum]

hi everyone,

I hope you're doing well.

I'm administrating à multi node Qliksense site.

1 central

1 failover

2 consumers

the cental is MANAGER and the rest of the node are WORKERS.

Everyday users complains that they can't run reload tasks (the restart of the scheduler service on all nodes solves the issue) and today I found a weird message on the logs:

The log is saying that : Scheduler is not an active master

I've made some research on that and I found nothing on the concept of "active master".

What does it mean "Active master" ? and how does a MASTER is supposed to run the task knowing that the MANAGER is the role that can launch the tasks...

Anyone faced this issue ?

Thanks 

Youssef

[rzenere_avvale]

Hey there @YoussefBelloum ,
I believe that the active master is an oversight; historically, QS Scheduler Service has 'Master' and 'Slave' roles, so I think it refers to that (and more specifically, to the fact that the node can start a task... as you would expect from a Manager/Master).
Apart from this, could you describe a bit more your environment? Users are trying to start tasks from the Consumer nodes? Or are they using APIs/...?

Riccardo

[YoussefBelloum]

Hi @rzenere_avvale 

Thanks for your reply.

I understand that the Master concept are not really replaced by manager concept. contrary to the "slave" concept that is replaced by the "worker" concept. I'm I right ?

Actually users connect to the consumers nodes ONLY, via a virtual proxy, and the load balacing configuration load balances the sessions only to the consumers nodes.

Users that are complaining about the reload tasks that are not running are launching the reloads from the hub.

but everytime we get the info, we try to start a reload task from the QMC and it does not work, reload tasks are completely blocked (QMC and hub), until we restart the scheduler service everywhere

[rzenere_avvale]

Yes and no; if I didn't lose any update, the concepts are the same between couples (so master = manager and slave = worker)
How are triggered the reloads from hub? Using the native button with the action 'Reload data'? Or with something else?

[YoussefBelloum]

They're using the "Reload Data" button and the "reload" button that you can find when you right click on an app (on a stream or the personal space).

[rzenere_avvale]

The in-app button with action "Reload data" works differently from the "reload" outside the app!
In the first case, you need permissions to update the published app (this is the same as doing a reload of an unpublished app). I wouldn't suggest to enable users to do this, since you also need to give visibility (read and update) to the script from what I recall.
In the second case, you need to check "only" the permissions of the reload task. See this KB article for more: Qlik Sense for Windows: How to allow task reloads on the Hub 

In both cases, Professional license seems to be needed (I don't recall this requirement for starting tasks from hub, you need to give it a try)

[YoussefBelloum]

I should have clarified the situation a little bit more.

 I am not asking the question of what is advisable to do or how to activate options.

The platform worked very well and we have both options open and functional, except that for weeks now we have had scheduler service problems..  (example of log already sent).

So basically it worked and it no longer works well.

When we restart the scheduler service it also works again all day.

My question is to understand why the log tell me that: scheduler is not an active master.. especially when all the nodes and services are up in the QMC and on all the servers