When the MR trains feature is enabled, the readyToMergeEE GraphQL API is called at an abnormally high frequency on the MR page.

Summary

environment：sass self-manage

When the merged results pipelines and merge trains are enabled, accessing any MR page will result in frequent calls to the readyToMergeEE GraphQL API, with the frequency increasing over time.

Steps to reproduce

Using self-managed as an example:

Navigate to the Settings -> Merge requests of any project.
Find and open the Enable merged results pipelines toggle, as well as the Enable merge trains toggle underneath it.
Access any MR page within the project.
Observe the network requests.

Example Project

What is the current bug behavior?

The number and speed of requests to the readyToMergeEE GraphQL API increase over time. 1678382158056

What is the expected correct behavior?

The readyToMergeEE GraphQL API is polled at increasingly longer time intervals.

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info


(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)
(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)
(we will only investigate if the tests are passing)

Possible fixes

/cc @mtan-gitlab-cn

由 Lixin Wan 编辑于 3月 10, 2023