We had an issue where if there is a timeout when loading metarecords, they will not be loaded until the next batch is created. This is because m.status.Update() will update the internal stats, but then the records are never swapped out on CQL error. This adds an (infinite) retry loop to load those records.
We had an issue where if there is a timeout when loading metarecords, they will not be loaded until the next batch is created. This is because m.status.Update() will update the internal stats, but then the records are never swapped out on CQL error. This adds an (infinite) retry loop to load those records.