Skip to content

Resolve "Error 500 loading status of Geo primary node when replication lag is high"

Brett Walker requested to merge 4773-replication-slots-max-retained-wal-bytes-too-small into master

What does this MR do?

Increases the size of the replication_slots_max_retained_wal_bytes in the GeoNodeStatus from an int4 to a bigint.

Why was this MR needed?

A 500 error was generated while loading the Geo Node Status when the replication lag was big enough to cause the replication_slots_max_retained_wal_bytes to grow over the size of a standard int.

Does this MR meet the acceptance criteria?

  • Changelog entry added, if necessary
  • [-] Documentation created/updated
  • [-] API support added
  • Tests added for this feature/bug
  • Review
    • [-] Has been reviewed by UX
    • [-] Has been reviewed by Frontend
    • Has been reviewed by Backend
    • [-] Has been reviewed by Database
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Squashed related commits together
  • [-] Internationalization required/considered
  • [-] If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
  • End-to-end tests pass (package-qa manual pipeline job)

What are the relevant issue numbers?

Closes #4773 (closed)

Edited by Brett Walker

Merge request reports