Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
hoangvvo
Partner - Contributor III
Partner - Contributor III

QMC - Is there a way to identify if a scheduler node is still available or not disconnected from Postgres

I have recently added 2 new Scheduler Node.

Added them to the existing load balance rule in qmc.

The new nodes are being picked up and task are being assigned over to it. They also have task queued up.

The problem is my 3 original nodes are not being being assign anything and no task are queue to those older nodes.

Auditing the rule shows with some apps selected shows that it is available to the nodes.

IF I restart repository services (which restarts everything else) on  the older nodes , cancel all queue, and restart all queued items again it starts to pick up into the older nodes again like what is expected.

But during middle of the day there's no way I can determine if there's a problem.

QMC shows that all nodes are active, all schedulers services available as well.

Is there a limitation on how many nodes (consumer, scheduler etc) are for each qlik cluster?

 

 

 

Labels (2)
1 Reply
hoangvvo
Partner - Contributor III
Partner - Contributor III
Author

I think this is related to the REPOSITORY SYNCHRONIZATION , the log file show:

6 20220524T191228.467-0600 WARN BI-Q9SERIM02 Synchronization.Repository.Repository.Core.Repository.Notification.ChangeMonitor 124 f39f386d-ff09-4cf6-813a-854ce1ba6c1e BI\qservices Connect to database for listing on NotifierSubscriptionChannel failed still trying. Failed attempts: 1 the database system is shutting down at Devart.Data.PostgreSql.k.a(PgSqlConnection A_0)↵↓ at Devart.Data.PostgreSql.k..ctor(PgSqlConnectionOptions A_0, PgSqlConnection A_1)↵↓ at Devart.Data.PostgreSql.j.a(q A_0, Object A_1, DbConnectionBase A_2)↵↓ at Devart.Common.DbConnectionFactory.a(DbConnectionBase A_0, q A_1)↵↓ at Devart.Common.DbConnectionFactory.b(DbConnectionBase A_0)↵↓ at Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection)↵↓ at Devart.Common.DbConnectionBase.Open()↵↓ at Devart.Data.PostgreSql.PgSqlConnection.Open()↵↓ at Repository.Core.Database.DatabaseChannelReceiver.<>c__DisplayClass7_0.<Start>b__0()↵↓ at Repository.Core.Database.DatabaseChannelSupport.WaitForConnect(Action connectAction) f39f386d-ff09-4cf6-813a-854ce1ba6c1e