'RecordInvalid: Position must be a valid json schema' during Direct Transfer MR migration
From https://gitlab.com/gitlab-org/gitlab/-/issues/431770#note_1746289895 (confidential, don't share any details here)
A number of project migrations using Direct Transfer captured failures with the following error message on merge requests relation:
RecordInvalid - Position must be a valid json schema
However, after comparing source & destination projects we could see that MR counters almost matched. Please note that the source project is live, where users add MRs, so it's not a 100% match.
Which makes me to believe that:
- Either the MRs were created on retry (do we have one on a batch level?)
- Subrelations failed to import and the import failures displayed are not for a merge request but for a subrelation (e.g. a note)
Investigate the root cause for these errors and see if these errors are retried and succeeded or a subrelation failed to import. Since this error is a timeout on a db level, is there a retry we can potentially add?
Edited by George Koltsov