Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
jan_lance
Partner - Contributor III
Partner - Contributor III

Not able to duplicate own apps with Load Balancing

Hi Folks,

we have a problem in a clustered enviroment:

Users are not able to duplicate their own apps in the hub in their own workspace.
They get this error:
2020-08-20 11_39_00-DELIN-QlikView-DEV - Remote Desktop Connection - __Remote.png

The cluster is with a central node and 2 rim nodes (PRD and DEV).
All node purposes are on "both".
The virtual proxy of the central node has the rim node engines for load balancing.

All published Apps should be run on the PRD node and unpublished apps should be run on the DEV node.
The Load Balancing rules are as follows:

Load Balancing RulesLoad Balancing Rules

Qlik Support told me this:

1. The engine used to duplicate the app doesn't have "permissions" to create the app in "my work"
2. When you try to duplicate the app in the stream, it will use the engine on the PROD node, but that engine is not able to create the app in "My work" as per LB rules
​3. Only the engine on DEV node is allowed to do that with those LB rules
​4. You can create an app because create an app will use the engine on the DEV node.
5. When you duplicate, it can only use 1 engine to do the whole process, and the PROD engine doesn't have rights to create apps in my work

So, ok now I know what is causing the problem but I still do not have a solution.
Unfortunately they could not help me further, so I am trying my luck here 🙂

Does anybody have an idea?

Labels (2)
1 Solution

Accepted Solutions
jan_lance
Partner - Contributor III
Partner - Contributor III
Author

@danielrozental_itm @mehmet_gencsoy 

Actually I DID find a workaround.

I just switched my Rim Nodes.

I just renamed PRD to DEV and DEV to PRD.

Turns out QlikSense always uses the first engine to duplicate the app.
The more you know...

Now the first engine is my DEV node and it works!

View solution in original post

14 Replies
Levi_Turner
Employee
Employee

Unfortunately you're encountering a deep issue in the way the Hub is rendered (bullet 5 is key here, one Engine does the duplicate thus it needs to be able to see the app and be able to create apps).

The work-around would be to duplicate in the QMC.

danielrozental_itm
Partner - Contributor
Partner - Contributor

Hi Jan, were you able to find a solution or a workaround?

mehmet_gencsoy
Luminary Alumni
Luminary Alumni

@Levi_Turner 

@jan_lance 

Is there any workaround possible?? We have the same issue.

Levi_Turner
Employee
Employee

@mehmet_gencsoy  : As I mentioned, above, the work-around is to duplicate from the QMC.

mehmet_gencsoy
Luminary Alumni
Luminary Alumni

@Levi_Turner  : Is there no way to duplicate from hub?? No way to extend the LB rules to get this work without error messages from hub?

Levi_Turner
Employee
Employee

The way the product is currently designed:

- An Engine delivers the Hub, aka the list of apps

- That Engine needs to have the app load balanced for the duplicate action to work

- Which Engine is selected is determined by a round robin algorithm

The combination of these is that there's not a way to have a reliable duplicate action from the Hub and use Load Balancing rules with any sophistication.

 

I'd suggest logging a feature request on the Ideas section of Community for this much needed improvement: https://community.qlik.com/t5/Ideas/idb-p/qlik-ideas

jan_lance
Partner - Contributor III
Partner - Contributor III
Author

@danielrozental_itm @mehmet_gencsoy 

Actually I DID find a workaround.

I just switched my Rim Nodes.

I just renamed PRD to DEV and DEV to PRD.

Turns out QlikSense always uses the first engine to duplicate the app.
The more you know...

Now the first engine is my DEV node and it works!

danielrozental_itm
Partner - Contributor
Partner - Contributor

Good to know, thanks for your reply Jan.

mehmet_gencsoy
Luminary Alumni
Luminary Alumni

Sorry that did not work for me. I have also renamed the nodes, but it did not help.

I have also problems with publishing apps. Do you have solved that issue also?

Which version are you using? Maybe it is an issue with our version. And do you have more details about your setup (virtual proxy, load balancing rules, etc.).

Thanks a lot.