If ?retrywrites=true, DeleteManyAsync() returns a MongoWriteException

Hi @Armies_Wagons,

Welcome to the MongoDB Community Forums! That does not sound right. Both deleteMany and deleteManyAsync still go through even if retryWrites=true is set. This does not look like a MongoDB issue. Hope that helps.

Thanks,

Rishit.

@Maithili_Kalkar the error you described does appear to come from the MongoDB server (mongo/src/mongo/db/ops/write_ops_exec.cpp at 00da7f442804d6118cc4bbc57caf9862e9811e2b · mongodb/mongo · GitHub), so it’s possible there may be an issue here.

Do you have a self-contained reproduction you could share that shows this failure in action?

@Maithili_Kalkar can you just confirm the version of the C# driver you’re using as well as the version of MongoDB you’re connecting to?

Also how is filter_id defined?

Hi @Maithili_Kalkar ,

Unfortunately, I’m not able to reproduce this error. I’m using MongoDB Community 3.6.0 with the C# driver 2.23.1 as you mentioned. The retryWrites option is set in my connection string as follows:

private string connectionString = "mongodb://localhost:27017/retryWrites=false";

The query used to perform the deleteManyAsync operation looks like this:

  var filter = Builders<Restaurant>.Filter.Eq(r => r.Cuisine, "Brazilian");
  var result = await _restaurantsCollection.Find(filter).ToListAsync();
  Console.WriteLine("Trying to Delete " + result.Count + " Restaurants");
  return await _restaurantsCollection.DeleteManyAsync(filter);

Not sure if that helps but if there’s any more information you can share or a sample zip file containing sample code to reproduce this, we’d be happy to take a look at it.

Thanks,

Rishit.

Thanks for confirming @Armies_Wagons.

Since the MongoDB driver wasn’t designed with CosmosDB in mind the failure conditions within that environment would be unpredictable, and may surface in (potentially confusing) ways such as this.