Qlik Community

Deployment & Management

Discussion board where members learn more about Qlik Sense Installation, Deployment and Management.

Announcements
IMPORTANT security patches for GeoAnalytics Server available to download: READ DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
Sivapriya_d
Creator
Creator

How to find the node connected in Qlik Sense(Qlik Sense Enterprise on Windows - Multi node Environment)


Hi All,

Is there a way to find the node which user is connected actively ?

I know from hub , Coumputername() can be used. Historical details can be found in Session Monitoring app.

But I want to find the node which user is connected actively. Lets say the user is accessing the published app and only read access is provided.

 

Thanks,

 

#QlikSense on windows,#Admin,#QlikSense

Labels (1)
1 Solution

Accepted Solutions
Lisa_Sun
Support
Support

Qlik Sense load balancing allow the workload balance among the nodes assigned for load balance in QMC.   This is managed automatically by the proxy service which will decide which repository service and engine to be assigned to.  

 

The default algorithm used for load balancing is round-robin, where the load is evenly distributed between the available nodes on the multi-node site. However, any subsequent sessions from the same user/client will open on the current engine node, instead of following the round-robin.

 

Since this is managed by intern service, the exact node handles this request only can be found from Qlik Sense logs and Session Monitoring app. 

 

Hope this helps. 

 

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

1 Reply
Lisa_Sun
Support
Support

Qlik Sense load balancing allow the workload balance among the nodes assigned for load balance in QMC.   This is managed automatically by the proxy service which will decide which repository service and engine to be assigned to.  

 

The default algorithm used for load balancing is round-robin, where the load is evenly distributed between the available nodes on the multi-node site. However, any subsequent sessions from the same user/client will open on the current engine node, instead of following the round-robin.

 

Since this is managed by intern service, the exact node handles this request only can be found from Qlik Sense logs and Session Monitoring app. 

 

Hope this helps. 

 

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!