I found this happens after mongo SYNC. After discussing with Ian, we think this issue might be the same/similar one we got in the prodstack(got timeout when mongo switches primary).
They mostly happen on the non-public cloud(probably low IOPS disk).
I would suggest we could have another run with the logging level set to WARNING.
I found this happens after mongo SYNC. After discussing with Ian, we think this issue might be the same/similar one we got in the prodstack(got timeout when mongo switches primary).
They mostly happen on the non-public cloud(probably low IOPS disk).
I would suggest we could have another run with the logging level set to WARNING.