Load Balance the "Monitoring apps" stream into Sub-Node.

[sten_still]

Hi Techies, 

I wanted to know is it possible to load balance the stream of "Monitoring Apps" which is by default it's in the stream. 

Currently, I have 1 CentralNode and 3 RimNodes at the moment, issue is missing data on the current one. 

Pls refer to the below image  

Notice the three lines(orange,green,yellow) is missing halfway at 05:00. 

Direct to the questions;

- This Operation Monitor is currently in the CentralNode, is this the reason why only CentralNode(blue) line appears ? 

- Is it possible if I load balance into whichever node (Node1,Node2 and Node3) so that i can get the data that is not delayed. 

- I understand the data actually delayed, instead of "missing" because if i checked on the next day. The data actually appear.

Hope someone can help me on this and clarify the things on the cache happenned in load balance. Thank you. 

[Alan_Slaughter]

Hi Sten_still, maybe the following articles will help:

1. https://community.qlik.com/t5/Knowledge/STT-Webinar-Configuring-Monitoring-Apps-in-Qlik-Sense/ta-p/1...

2. https://community.qlik.com/t5/Knowledge/Qlik-Sense-Enterprise-Move-reloads-to-RIM-nodes-and-exclude/...

[sten_still]

Dear Alan,

Thank you for the articles.

My concern on this is the current ops monitor  when last reloaded on today is actually delayed, it's incomplete for today's ops monitor data.

Meaning i will get to view all the sessions and complete data on the next day. Is there any way to get data tally with the other nodes because currently only central nodes showing. The other central will appear on the next day. 

On the below image, the ops monitor last reloaded at 11.40. Only the central node has the data.

[Alan_Slaughter]

Hi sten_still, monitoring apps only collect from the latest logs that have been generated. I would suggest following the multinode setup. 

https://help.qlik.com/en-US/sense-admin/May2022/Subsystems/DeployAdministerQSE/Content/Sense_DeployA...

[Albert_Candelario]

Hello @sten_still ,

Are you saying data from other nodes are only loaded when logs have been archived? 

Cheers,

Albert

[sten_still]

Hi @Albert_Candelario yes,

the log data from other nodes are available about one day later. For the last reloaded data is not there until i waited for next day.

[Albert_Candelario]

Hello @sten_still ,

to verify what I suggested of the achieved logs, could you restart the services on the RIM nodes and afterwards reload the app and see if the latest data has been fetched?

If is PROD environment you might need to find a suitable time.

I suggesting such based on How To Check Archived log folder - Qlik Community - 1715297

Qlik Sense Enterprise on Windows automatically archives log files when:

1. The log file reaches a maximum of 8 MB
2. Every 12 hours
3. The Qlik Sense Services are restarted

Cheers,

Albert

[sten_still]

Dear @Albert_Candelario , 

I have done the following details as you suggested to restart the services. Currently there are on multinodes, the services i have restarted by following the link Restart QlikSense Services.

Stop the Rim and Start from Central. 

Unfortunately the log still delayed from the time where it last reloaded which the data will be available on the next day.

Besides, during restarting the services i found out some of the nodes are offline and 'has stopped', (1) even all the services are running,(2). 

(1)

 (2)

After checking on the log files, i found out these error. Internal Server Error . Followed the following instruction but still having the offline nodes and non working nodes. 

I have attach the following log files for you to revive regarding this case. This is for the hostname rim3. 

[Albert_Candelario · Accepted solution]

Hello @sten_still ,

Thanks for posting and thanks for sharing the issue is still not resolved.

Did you manually check after the services restart if the logs were moved to the archieved folder?

Regarding the new issue you have mentioned I spot this error:

Something went wrong: 53300: remaining connection slots are reserved for non-replication superuser connections Npgsql.PostgresException (0x80004005): 53300: remaining connection slots are reserved for non-replication superuser connections↵↓ at Npgsql.NpgsqlConnector.<>c__DisplayClass161_0.<<ReadMessage>g__ReadMessageLong|0>d.MoveNext()↵↓--- End of stack trace from previous location where exception was thrown ---↵↓ at Npgsql.NpgsqlConnector.<>c__DisplayClass161_0.<<ReadMessage>g__ReadMessageLong|0>d.MoveNext()↵↓--- End of stack trace from previous location where exception was thrown ---↵↓ at Npgsql.NpgsqlConnector.Open(NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)↵↓ at Npgsql.ConnectorPool.AllocateLong(NpgsqlConnection conn, NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)↵↓

Kindly can you let us know the # of connection allow on your database, as per the error seems is too low, please check:
Postgres: FATAL: remaining connection slots are re... - Qlik Community - 1715939

Cheers,

Albert

[Albert_Candelario · Accepted solution]

@sten_still ,

For "the task was cancelled error" also check An App fails to distribute to Cloud Cloud, App Dis... - Qlik Community - 1844121

Cheers,

Albert