Skip to main content
Buffer Query Error

Buffer Query Error explained.

Praise Magidi avatar
Written by Praise Magidi
Updated over 2 weeks ago

Message

Executor error during getMore :: caused by :: collection dropped.

Cause

The Buffer being read from in this step query has been purged while the query was being executed. The purge either was likely triggered by another step in this Flow, or another Flow that is executing in parallel to this one, or possibly a manual purge executed on the Synatic admin portal.

Resolution

Look for a Buffer Destination step in the Flow where this error occurred. Also, look for Flows being executed at the same time as the Flow where this error occurred, and check for Buffer Destination steps. If any of those Buffer Destination steps trigger a purge of the Buffer being queried, consider redesigning some of the Flow execution to avoid purging the Buffer while it is being queried.

If the Buffer is being purged in the same Flow that is querying it, with the objective being to update the data in the Buffer after the flow has processed it, consider removing the purge and updating the data instead of inserting it.

If the Buffer is being purged in a different Flow executing at the same time as the Flow where this error occurred, your Flows are likely prone to this error or potentially even data loss due to the purging of data before it can be processed. Evaluate how the Flows are triggered, look at their objectives, and assess if there is any alignment that can be done to ensure these problems can be avoided. It might be worth using separate Buffers for "Unprocessed" and "Processed" records.

If the purge was triggered manually, this error is an isolated incident. Ensure that you don't purge a Buffer manually while any Flows that reference the Buffer are running.

Error Detail

{
"errorResponse": {
"ok": 0,
"errmsg": "Executor error during getMore :: caused by :: collection dropped. UUID de031c8d-30af-XXXX-XXXX-XXXXXXXXX",
"code": 175,
"codeName": "QueryPlanKilled",
"$clusterTime": {
"clusterTime": {
"$timestamp": "7462477214051731192"
},
"signature": {
"hash": "s+uxpAomu8g/Oii3rpBKGeLshTY=",
"keyId": {
"low": 6900,
"high": 1725399129,
"unsigned": false
}
}
},
"operationTime": {
"$timestamp": "7462477214051731192"
}
},
"ok": 0,
"code": 175,
"codeName": "QueryPlanKilled",
"$clusterTime": {
"clusterTime": {
"$timestamp": "7462477214051731192"
},
"signature": {
"hash": "s+uxpAomu8g/Oii3rpBKGeLshTY=",
"keyId": {
"low": 6900,
"high": 1725399129,
"unsigned": false
}
}
},
"operationTime": {
"$timestamp": "7462477214051731192"
},
"statusCode": 500,
"stepType": "Destination",
"stepName": "HTTP",
"stepId": "06XXXXX0-0XXX-49fd-99a0-XXXXXXXX7",
"mapStepId": "pUHpXUy1J",
"mapStepPath": "9H910wirU.pUHpXUy1J",
"mapStepType": "Step",
"module": "Basic",
"commandProcessingError": null
}

Did this answer your question?