Error starting sync

MongoDB Atlas App Services & Realm Atlas Device Sync
,
1

We recieve the following error from a partition based sync realm app:

Enabling Sync …approximately 34283/140520 (24.40%) documents copied
Errors… db.tbl: “encountered error when flushing batch: error in onBatchComplete callback: error integrating batch: error performing database transaction to flush translator batch: inserting entries into client history failed: timed out while checking out a connection from connection pool: context deadline exceeded; maxPoolSize: 20, connections in use by cursors: 0, connections in use by transactions: 0, connections in use by other operations: 10”, db.tbl: “encountered error when flushing batch: error in onBatchComplete callback: error integrating batch: error performing database transaction to flush translator batch: inserting entries into client history failed: context deadline exceeded”, db.tbl: “encountered error when flushing batch: error in onBatchComplete callback: error integrating batch: error performing database transaction to flush translator batch: failure from transaction callback in batch upload integration: error flushing unsynced documents: error flushing unsynced documents cache: context deadline exceeded”, db.tbl: “encountered error when flushing batch: error in onBatchComplete callback: error integrating batch: error performing database transaction to flush translator batch: failure from transaction callback in batch upload integration: error flushing unsynced documents: error flushing unsynced documents cache: context deadline exceeded”, db.tbl: “encountered error when flushing batch: error in onBatchComplete callback: error integrating batch: error performing database transaction to flush translator batch: failure from transaction callback in batch upload integration: error flushing unsynced documents: error flushing unsynced documents cache: context deadline exceeded”, db.tbl: “encountered error when flushing batch: error in onBatchComplete callback: error integrating batch: allocating new client versions failed: connection(…) incomplete read of message header: context canceled”

Any idea of what can be done about it?

2

Hi, we have a ticket to clean up this message but this is a transient mongodb error that one of our writes was rejected (cluster is overloaded, primary changing, etc) and we had to error out and restart (should happen automatically). It looks like your app is up and running though and writes are processing quickly. Let me know if there is anything else we can help with.

3

hello, I am facing the following problem in this api route. https://vila.up.railway.app/post/index/most-recent-card/popup

there are some other routes bursting this problem from what I saw the problem is in mongo