Write Conflict how it actually works

[MaBeuLux88_xxx (Maxime Beugnet)]

Hi @Nishant_Kumar4,

Here are a couple of other posts in the forum that can help maybe:

Write conflict in transaction

I have an application that tries to update the same row in a collection in 2 separate threads at the same time. Each thread has its own connection the MongoDB server and has started a transaction. Thread 1 has altered the row and the 2nd thread tries to update the same row when MongoDB returns the write conflict error. The 2nd thread waits 5 millisecs and then tries to update the row again, when MongoDB returns transaction aborted. Each thread is updating and inserting into multiple documents …

Understanding locking within transactions (and how it deals with high concurrency)

TLDR: Do the locks created by operations that occur within mongodb transactions unlock immediately after the operation is complete or after the transaction is complete (committed/aborted)? The background: I’m using mongo to model the lobby state of a game round that clients are able to join and I would just like some clarification on how the use of transactions and correct data modeling can allow me to handle a high amount of concurrent requests while eliminating the risk of race conditions an…

Now back to your issue: in your code, I don’t see you use the API for transactions.

Transactions — MongoDB Manual

Without a transaction, there is no reason for a write conflict as all the operations would then be considered atomic (and transactional on their own).

I hope this helps.
Cheers,
Maxime.