topic Slave node not found - reload can only be done in central node in Management & Governance

Slave node not found - reload can only be done in central node

Huiying — Thu, 29 Aug 2019 10:53:27 GMT

We have 4 nodes with scheduler service: central node - Master and Slave, failover node - slave, scheduler node1&2 - slave.

For some reason, only central node does all the reload. If I change central node to only Master, reload task will give 'no scheduler node found' error.

Central node has 5 services running: QRS, QES, QSS, QPS, QPR

failover node has 4 services running: QRS, QES, QSS, QPS

scheduler nodes have 3 services running: QRS, QES, QSS

I have checked 5050 & 5151 ports from all nodes.

After change central node to Master only, i have restarted all services on central.

Now don't know where to check next to fix the issue.

In virtual proxy load balancing, failover node is load balancing central node's load. so at least failover should be able to get task from central node, right?

confused...

Best regards,

Susan

Re: Slave node not found - reload can only be done in central node

Levi_Turner — Thu, 29 Aug 2019 18:27:27 GMT

Do any of the RIMs have the app or apps load balanced to them? For example, out of the box, Qlik Sense ships with the Load Balancing rule named ResourcesOnNonCentralNodes, whose effect is that apps published to the monitoring apps stream are not load balanced to RIM nodes. You of course can create your own to load balance all apps or only a sub set of apps across RIMs on a multi-node site.

Re: Slave node not found - reload can only be done in central node

eric_careta — Tue, 16 Nov 2021 11:07:19 GMT

Hi @Huiying

I have the same trouble.

Did you resolve it?

Thanks!