I'm facing an issue with restoring a MongoDB backup to Azure Cosmos DB using mongorestore - it seems to trigger burst limits, causing records to be dropped. After digging into this, it looks like provisioning a really high amount of Request Units (RUs) is the suggested solution, but I'm not entirely sure if that will actually solve the problem. I'm looking for any workarounds or tips on how to handle this situation effectively.
2 Answers
Honestly, I've found that Azure Cosmos DB can get pretty pricey. It seems to work well on a smaller scale, but when you try to scale it, the costs can skyrocket compared to what you initially expected.
Are you using partitions? If you increase your RUs, it might lead to more partitions, which can create a cycle of needing more RUs to maintain those partitions. It can get really complicated and frustrating!
I just want a straightforward restore process, but it feels impossible right now. This has been the most frustrating experience I've ever had!