Sign in or sign up before continuing. Don't have an account yet? Register now to get started.
Register now

Geo: Investigate "synced" uploads on GPRD whose files do not exist

There were 7297, which was strange.

I took the first one, and its registry showed a successful sync. When I marked it for retry, and executed FileDownloadService for it, it downloaded the file and marked the registry as synced again. Now the Upload responds with true to exist?.

  • 114 uploads were later destroyed - OK
  • 32 now have a file - OK
  • 1074 are missing on primary - OK
  • 6109 remaining - NOT OK
    • File exists on the primary
    • Marked synced
    • Not marked missing on primary
    • All are project file uploads across 326 projects
    • The registries were all created after 08 Feb 2018
    • The uploads were all created after 12 Apr 2017
  • How did this happen for these cases?
    • Were their files deleted after successful sync?
    • Were they moved on the primary, and their paths changed as well?
  • What should be done in the code, and/or manually?
    • Verification https://gitlab.com/gitlab-org/gitlab-ee/issues/5591 would catch this, and auto retry would fix it. Is that sufficient?
Edited May 10, 2018 by Michael Kozono
Assignee Loading
Time tracking Loading