Hi!! I was running a python application on shared M0 cluster and google cloud and was able to insert 60000 data via insert_many in pymongo without write conflict, as soon as I upgraded the cluster to dedicated using Azure the exact same script started returning Writer Conflict, I tried to use AWS Cloud, upgrading again to M20 , but with no success. How does the shared cluster not return Writer Conflict Error whilst the dedicated, supposedly more potent, does?
Hi @Marina_De_Souza_Ripper - Welcome to the community.
Could you provide the following information:
- insert_many pymongo script used? (please redact any personal or sensitive information)
- full write conflict error
Additionally, can you confirm if the below steps are somewhat correct in terms of producing this issue?
- Created M0 GCP free tier cluster
- Ran the insert_many pymongo script against the cluster in 1.
- Upgraded the same M0 cluster in 1. to M10 Azure
- Ran the insert_many pymongo script again against the upgraded cluster (now M10)
- Received write conflict
- Upgraded the M10 Azure cluster to M20 AWS
- Ran the insert_many pymongo script again against the upgraded cluster (now M20)
- Received write conflict error
Additionally, the write conflict mentioned is unlikely to be caused by the underlying cloud provider since it is generally the result of two or more processes trying to update the same document.
Regards,
Jason
1 Like