Geo group issues requiring attention

Hi @fzimmer,

Here is a list of feature proposals without a milestone.

We would like to ask you to determine whether this issue should be scheduled or closed. For each issue please:

  • Close the issue out if it is no longer relevant or a duplicate.
  • Assign either a versioned milestone, the %Backlog or the %Awaiting further demand milestone.

For the issues triaged please check off the box in front of the given issue.

Please work with your team to complete the list this week.

  • #9341 (closed) Geo: Backfill GitLab Pages on secondaries ~"Geo", ~"Geo Replication/Sync", devopsenablement, feature
  • #7617 (closed) Geo: "Recheck"/"Resync" button on a primary ~"Geo", Geo Administration, devopsenablement, feature
  • #7484 (closed) Geo: Verify correct user_mapping configuration for FDW using SystemChecks ~"Geo", Geo Administration, devopsenablement, feature
  • #7258 (closed) Geo: Automatically heal uploads on secondaries ~"Geo", ~"Geo DR", ~"Geo Verification/Accuracy", devopsenablement, feature
  • #7257 (closed) Geo: Automatically verify uploads on secondaries ~"Geo", ~"Geo DR", ~"Geo Verification/Accuracy", devopsenablement, feature
  • #7184 (closed) Constantly verify uploads on Geo primary (incl non Geo instances) ~"Geo", ~"Geo DR", ~"Geo Verification/Accuracy", devopsenablement, feature
  • #7029 (closed) Data retention for Geo deleted events ~"Geo", ~"Geo Performance", auto updated, awaiting feedback, devopsenablement, feature
  • #6267 (moved) Geo: Runner registration when secondary is promoted to primary ~"Geo", ~"Geo DR", auto updated, devopsenablement, feature, ~"runner"
  • #6109 (closed) Improve broadcast message cache management ~"Geo", ~"Geo Replication/Sync", devopsenablement, feature, regression:10.x
  • #6080 (closed) Provide some warning / error in case of gitlab-secrets.json mismatch on Geo nodes ~"Geo", Geo Administration, customer, devopsenablement, feature
  • #5985 (closed) Documentation : Improve planned failover documentation based on staging experience 1st contribution, ~"Documentation", ~"Geo", auto updated, awaiting feedback, devopsenablement, feature
  • #5829 (closed) Geo: Improve LogCursor log content and debug mode ~"Geo", Geo Administration, customer, devopsenablement, feature
  • #5747 (closed) Geo - Check repository verification failures on primary/secondary nodes ~"Geo", Geo Administration, UX, devopsenablement, feature
  • #5698 (closed) Handle accepting terms for Geo ~"Geo", auto updated, devopsenablement, feature
  • #5447 (closed) Geo: Use git clone for first sync instead of git fetch ~"Geo", ~"Geo Performance", devopsenablement, feature


This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals. For more information please refer to the handbook:

  • https://about.gitlab.com/handbook/engineering/quality/guidelines/triage-operations/#current-packages
Edited Jun 11, 2019 by Fabian Zimmer
Assignee Loading
Time tracking Loading