topic Re: Separate Qlik Sense Scheduler in Management & Governance

Separate Qlik Sense Scheduler

balajibc64 — Tue, 07 Mar 2023 08:41:50 GMT

Hi, Need to run a task based on multi node like separating the task. Eg. I'm having 2 task, one task is taking more time to complete but other task will run soon. But because of 1st task, the 2nd task is taking more time to complete.

How to overcome this issue.? How to separate both task and run in different nodes or whatever.

Kindly suggest. Thanks

Re: Separate Qlik Sense Scheduler

Jay_Brown — Tue, 07 Mar 2023 13:17:46 GMT

Hello @balajibc64 , thanks for posting!

Have a look at the following article:
https://community.qlik.com/t5/Official-Support-Articles/Load-Balancing-in-Qlik-Sense-Enterprise-on-Windows/ta-p/1715174

and Community discussion:
https://community.qlik.com/t5/Deployment-Management/scheduler-load-balancing/td-p/1643072

And let us know; Are these tasks chained?

Re: Separate Qlik Sense Scheduler

balajibc64 — Tue, 07 Mar 2023 16:28:53 GMT

Yes @Jay_Brown Task chained. it will runs continuous one after another based on schedule time.

Re: Separate Qlik Sense Scheduler

balajibc64 — Wed, 08 Mar 2023 11:36:36 GMT

Hi @Jay_Brown Thanks for your response. I read this article and did something based on load balancing. But my RIM node is showing has stopped.

Let me say few details about my requirement.

1. we are having 2 servers. when i looked into the 2 servers nodes both are showing the central node.

2. Based on the article i have added the custom property like node type. custom value also mentioned like dedicated. After that I have created the another node called rimnode.

Central node refer to First server

Rim Node I gave to refer second server.

But for RIM node service not running. It showing error like "Engine Status unknow never contacted"

Could you please check this and help me for the same.

Re: Separate Qlik Sense Scheduler

Jay_Brown — Mon, 13 Mar 2023 18:31:51 GMT

Hello @balajibc64 ,

This is usually some port issue. Have you verified all the ports are reachable via PowerShell?

Check this article:
https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Management-console-shows-Engine-status-unknown-never/ta-p/1710586

Re: Separate Qlik Sense Scheduler

balajibc64 — Tue, 14 Mar 2023 05:34:26 GMT

No @Jay_Brown I didn't tired to verified about ports. From where need to verify ? In Central or RIM node. Moreover, I created the RIM node but I didn't change the server from central node to rim node. Because previously when i installed Qlik in both the server like Central node only.

Re: Separate Qlik Sense Scheduler

Jay_Brown — Thu, 16 Mar 2023 17:01:23 GMT

Hello @balajibc64 ,

For a multi-node configuration you will probably want to back up the environment, uninstall Sense from the second node, and install the second node as a rim using the Join a cluster option.

https://help.qlik.com/en-US/sense-admin/February2023/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Installing-Qlik-Sense-multi-node.htm#Installi3

To answer your question about testing ports, you will want to test in both directions, Central to Rim, and Rim to Central. If ports are not being blocked you should be able to install per the link above.

Please let us know if this helps!

Re: Separate Qlik Sense Scheduler

balajibc64 — Mon, 20 Mar 2023 07:03:13 GMT

@Jay_Brown Thanks. Yes I tried but while installing facing the issue DB connectivity. Facing error this stage,

"Database could not be reached"

Re: Separate Qlik Sense Scheduler

Jay_Brown — Mon, 20 Mar 2023 15:05:14 GMT

Hi @balajibc64 , can you verify connectivity from the rim node to the database server or central node?

For example, if your central node hosts the database and is named 'qlikserver1', use the following command in PowerShell on the rim node:
testNetConnection -servername qlikserver1 -port 4432

What error are you getting otherwise?

Re: Separate Qlik Sense Scheduler

balajibc64 — Mon, 20 Mar 2023 17:30:34 GMT

Hi @Jay_Brown ok will check. Yes, Getting error like "Database could not be reached"