Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Having two instances of DQM square mirror running in parallel degrades the service #17

Open
nothingface0 opened this issue Jul 2, 2024 · 0 comments

Comments

@nothingface0
Copy link
Contributor

If running two separate DQM square mirror instances, both try to get information from the P5 machines at the same time, by using the playback RUBU as an intermediate. This doesn't work well, which is why the cmsweb-test4 deployment needs to ask for updates as little as possible (currently once per half an hour).

If, for example, the service is running at the same update rate (every 30s) in two separate instances, the result is that neither is updated in time:

image

What needs to be investigated:

  • Perhaps it's the get_cluster_status endpoint which slows down the RUBU by having to open websockets to each of the FU machines?
  • Could the requests from the mirror be minimized, by aggregating them so that one request gets all the updates for one host?
  • Is it related to the fff_dqmtools service itself?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant