Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
JS part of the pcsd web UI refreshes cluster status every 30ish seconds. Upon receiving the refresh request, pcsd backend gathers the status by running several cluster tools. If several users are viewing the same cluster or have the web UI opened in multiple tabs, each of them is asking for the cluster status individually and all such requests are handled independently. This can cause a significant load in the cluster even if load related to a single status refresh is reasonable.
The idea is:
* whenever a user starts viewing a cluster in web UI, start a loop for loading its status in the backend
* the loop automatically loads cluster status every 30ish seconds (this may be configurable) and caches it
* when web UI asks for cluster status, it gets response immediately from the cache
* if the loop detects nobody asked for cluster status for a while, it stops to prevent unnecessary load
* we may want to have a way to force loading the status / override the cache
In a similar way, we need to deal with the clusters overview view.
Version-Release number of selected component (if applicable):
pcs-0.10.4-5.el8
How reproducible:
always, easily
Steps to Reproduce:
1. display a cluster in web ui
2. run top on cluster machines, observe refreshing the status periodically causes load
3. display the same cluster in more browsers or tabs
4. run top on cluster machines, observe refreshing the status periodically causes bigger load
Actual results:
each web UI instance loads the cluster status individually causing extra load
Expected results:
the cluster status is refreshed once in while no matter how many clients are connected keeping the load at reasonable levels
Comment 8RHEL Program Management
2023-09-22 18:51:30 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 9RHEL Program Management
2023-09-22 18:51:53 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.