GET requests for an atom feed of issues sometimes seem to cause writes to the primary
As discovered while investigating https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/549. And added by Andrew in https://gitlab.com/gitlab-com/gl-infra/production/-/issues/2579#note_402995399
It looks like a get to Projects::IssuesController#index.atom
sometimes go to the primary through a method_missing
:
PG::QueryCanceled: ERROR: canceling statement due to statement timeout
ee/lib/gitlab/database/load_balancing/connection_proxy.rb:86:in `block in write_using_load_balancer',
ee/lib/gitlab/database/load_balancing/load_balancer.rb:84:in `block in read_write',
ee/lib/gitlab/database/load_balancing/load_balancer.rb:134:in `retry_with_backoff',
ee/lib/gitlab/database/load_balancing/load_balancer.rb:83:in `read_write',
ee/lib/gitlab/database/load_balancing/connection_proxy.rb:80:in `write_using_load_balancer',
ee/lib/gitlab/database/load_balancing/connection_proxy.rb:60:in `method_missing',
app/views/projects/issues/index.atom.builder:6,