Does CosmosDB for MongoDB honour the ordered writes parameter for inserts during bulk write operations?

Question

Does CosmosDB for MongoDB honour the ordered writes parameter for inserts during bulk write operations?

Kiruphasankaran Nataraj 0

I'm using the MongoDB Java Driver version 4.8.2 to insert around 10000 documents with upsert enabled using bulk write operations. I've enabled ordered writes and disabled the Server Side Retry feature. My MongoDB server version is 4.2.

However, I'm experiencing issues where the documents are not inserted in order and the operation throws an exception due to Server Side Retry being disabled. I'm wondering if CosmosDB honors the ordered writes parameter when performing inserts during bulk write operations.

Additionally, the error index returned from the bulk write exception doesn't seem to correspond to the first non-written document in the list. Is there a recommended way to handle errors due to throttling when Server Side Retry is enabled?

Oury Ba-MSFT 20,911 Reputation points Microsoft Employee Moderator

2023-07-31T22:20:59.49+00:00

@Kiruphasankaran Nataraj Thank you for reaching out.

My understanding is that you are experiencing an error index returned from the bulk write exception. You have enabled writes and disabled the server side retry failure.

Please kindly share the full error message you are getting.?

Regards,

Oury
Kiruphasankaran Nataraj 0 Reputation points

2023-08-01T09:02:00.6566667+00:00
@Oury Ba-MSFT Thanks for the response.

Yes, I'm experiencing an issue with the error index returned in the MongoBulkWriteException that is thrown due to the Server Side Retry being disabled.

Also, I have ordered writes enabled while performing the bulk write but it looks like it is not being honoured. Say I have a list of 10000 ReplaceOneModels with upsert set to true, the write fails due to throttling by throwing a MongoBulkWriteException. Since I have ordered writes enabled while performing the bulk write, the expectation is that the documents after the first failed document should not have been inserted (from the MongoDB driver Javadoc - If true, then when a write fails, return without performing the remaining writes. If false, then when a write fails, continue with the remaining writes, if any. Defaults to true.). But I could see some documents in the middle of the list being present in the collection even though I have ordered writes turned on. So, I had the doubt of whether CosmosDB actually honours this flag for bulk inserts.

The error message received from the exception due to throttling while inserting 10000 documents:

com.mongodb.MongoBulkWriteException: Bulk write operation error on server xxx.mongo.cosmos.azure.com:10255. Write errors: [BulkWriteError{index=53, code=16500, message='Error=16500, RetryAfterMs=4, Details='Batch write error.', details={}}, BulkWriteError{index=54, code=16500, message='Error=16500, RetryAfterMs=4, Details='Batch write error.', details={}}, BulkWriteError{index=55, code=16500, message='Error=16500, RetryAfterMs=4, Details='Batch write error.', details={}},... (clipped due the message being large)

2 answers

Your answer

Oury Ba-MSFT 20,911 Reputation points Microsoft Employee Moderator

2023-07-31T22:20:59.49+00:00

@Kiruphasankaran Nataraj Thank you for reaching out.

My understanding is that you are experiencing an error index returned from the bulk write exception. You have enabled writes and disabled the server side retry failure.

Please kindly share the full error message you are getting.?

Regards,

Oury
Kiruphasankaran Nataraj 0 Reputation points

2023-08-01T09:02:00.6566667+00:00

@Oury Ba-MSFT Thanks for the response.

Yes, I'm experiencing an issue with the error index returned in the MongoBulkWriteException that is thrown due to the Server Side Retry being disabled.

Also, I have ordered writes enabled while performing the bulk write but it looks like it is not being honoured. Say I have a list of 10000 ReplaceOneModels with upsert set to true, the write fails due to throttling by throwing a MongoBulkWriteException. Since I have ordered writes enabled while performing the bulk write, the expectation is that the documents after the first failed document should not have been inserted (from the MongoDB driver Javadoc - If true, then when a write fails, return without performing the remaining writes. If false, then when a write fails, continue with the remaining writes, if any. Defaults to true.). But I could see some documents in the middle of the list being present in the collection even though I have ordered writes turned on. So, I had the doubt of whether CosmosDB actually honours this flag for bulk inserts.

The error message received from the exception due to throttling while inserting 10000 documents:

com.mongodb.MongoBulkWriteException: Bulk write operation error on server xxx.mongo.cosmos.azure.com:10255. Write errors: [BulkWriteError{index=53, code=16500, message='Error=16500, RetryAfterMs=4, Details='Batch write error.', details={}}, BulkWriteError{index=54, code=16500, message='Error=16500, RetryAfterMs=4, Details='Batch write error.', details={}}, BulkWriteError{index=55, code=16500, message='Error=16500, RetryAfterMs=4, Details='Batch write error.', details={}},... (clipped due the message being large)

Answer 1

Oury Ba-MSFT 20,911 Microsoft Employee Moderator

@Kiruphasankaran Nataraj Thank you for getting back and for sharing the error message.

Azure Cosmos DB for MongoDB operations may fail with rate-limiting (16500/429) errors if they exceed a collection's throughput limit (RUs).

You should not do ordered writes, it reduces performance: Optimize write performance in the Azure Cosmos DB for MongoDB | Microsoft Learn

Server side retry should be enabled to prevent rate limiting errors.

Please turn off retryable writes- I don't think it's needed since network errors don't appear to be an issue. With this feature, you can't do bulk unordered writes, which will prevent you from implementing the recommendation in the first point. 4.2 server version supported features and syntax in Azure Cosmos DB for MongoDB | Microsoft Learn

Hope that clarifies your ask.

Please don't forget to mark as accept answer if the reply was helpful.

Regards,

Oury

Kiruphasankaran Nataraj 0 Reputation points

2023-08-02T06:57:04.7766667+00:00

@Oury Ba-MSFT Thanks for the answer.

I have retryable writes turned off while performing the bulk write. As you mentioned, the network is not an issue. But I want to perform ordered writes intentionally and while performing them, it looks like its not behaving as per the MongoDB Javadoc. I could see some documents have been inserted in the collection that are present after the first failed document. Hence, I still have a clarification regarding whether CosmosDB for MongoDB honours the ordered writes property if it is set to true.
Oury Ba-MSFT 20,911 Reputation points Microsoft Employee Moderator

2023-08-02T17:27:08.52+00:00

Kiruphasankaran Nataraj

Thank you for getting back. I found that your recent engagement to the above question was rated low.

I will appreciate if you can create a support ticket so we can further investigate this offline. Please do let me know if you dont have a support plan.

Regards,

Oury
Oury Ba-MSFT 20,911 Reputation points Microsoft Employee Moderator

2023-08-03T20:54:25.8766667+00:00

Kiruphasankaran Nataraj

Were you able to create a support ticket. If not, please let me know. You can send an email to azcommunity@microsoft.com with your subscription ID and please mention in the subject Line: ATTN: Oury so I dont. miss it.

Regards,

Oury

Answer 2

Nguyen Le 0

I'm using the MongoDB C# Driver version 2.24.0 to insert around 7.7 million documents with IsOrder set to false using bulk write operations.
The request rate unit is manual set are 10000 RU
I've enabled the Server Side Retry feature to prevent rate limiting errors. My Azure Cosmos DB for MongoDB server version is 4.2.
I get poor performance around 15 hours to finish insert.
Can anybody help me to explain what happen?

Oury Ba-MSFT 20,911 Reputation points Microsoft Employee Moderator

2024-04-16T18:49:14.4066667+00:00

Nguyen Le

Could you please create a new thread .

Share via

Does CosmosDB for MongoDB honour the ordered writes parameter for inserts during bulk write operations?

2 answers

Your answer