Large node selection using tags within jobs causes entire browser application to go into waiting state
Marcussafar opened this issue · comments
Describe the bug
When large amounts of nodes are selected within an already created Rundeck Job using a tag filter selection under "Change the Target Nodes" area, if the selection has too many nodes the browser UI will be loaded/slowed down and become almost completely unusable.
We have various tag selection filters, some with over 5000 nodes to be selected, but when anything above 500 is selected, the browser will bring up a "Wait" notification alert or none at all depending on the activity in the browser.
My Rundeck detail
- Rundeck version: 5.1.2
- install type: Docker
- OS Name/version: Ubuntu 22.04
- DB Type/version: AWS Aurora RDS MySQL
To Reproduce
Steps to reproduce the behavior:
- Create a rundeck instance with more than 1000 nodes and tags associated with them.
- Click on a job and click "Change the Target Nodes" and click a tag filter with a large set of nodes
- Wait for the browser UI to go into a "Waiting" notification status.
Expected behavior
Older versions of Rundeck (below version 3) do not have this problem. In fact, my company still has an older version (2.10) we are trying to migrate from which does not have this problem and its causing us to delay a full migration.
Desktop (please complete the following information):
- OS: Ubuntu
- Browser: Chrome
- Version Version 115.0.5790.98 (Official Build) (64-bit)
Additional context
We tried running version 4.17 of Rundeck last year and experienced this same issue.