Quota exceeded. Consider creation of a new collection

Question

I receive a Microsoft.Azure.Documents.ForbiddenException, message: {"Errors":["Quota exceeded. Consider creation of a new collection."]} but I'm not entirely sure why. The Azure portal reports a database account storage usage of 3.15GB. The documentation says the 'Minimum Allocated Storage per collection with minimum 1 document' is 3.3GB.

Does the error I get concern the size quotum of 3.3GB? So where are the other 150MB?

Or is it another quotum I'm hitting? If so, what quotum is that?

And yet another question (sorry): what is the elasticity of a collection, which can vary between 0-10GB?

Answer 1

@rwwilden, Collections scale up to 10 GB in increments of 1GB. We investigated your endpoint and found that there was a delay in reporting the usage of space used. This issue has been resolved, and we noticed your collection is now scaled up to 4GB. The collection will scale up to 10GB as long as there is capacity available in the endpoint.

And thanks for your excellent article on DocumentDB performance at InfoQ. We would love to connect and understand any performance bottlenecks, or help you fine tune your experiment. Please send me a note at <first name> . <last name> @ microsoft dot com, in case you are interested.

Answer 2

Thanks for your answer. I tried creating another document but I still see the Quota exceeded message... And the portal still reports that I use 3.15GB.

Answer 3

@Aravind, I tried to contact you at "Aravind.Ramachandran at microsoft dot com" but the message bounces with a 'email address can not be found or is invalid' message...

Answer 4

Aravind and I work together on DocumentDB. Feel free to reach out to me at johnmac at Microsoft dot com. Thanks!

Answer 5

I had direct contact with the DocumentDB team concerning this issue and it's fixed now. It appears there were two issues, although I don't have the details.

First fix (9-10-2014): 'We have also investigated the quota error you ran into. We root caused this and deployed a fix for the issue. Can you confirm that you are no longer seeing the error?'

Second fix (9-11-2014): 'We discovered an issue that was blocking your collection from scaling. We believe we’ve resolved the issue now. Can you confirm you’re no longer seeing this error?'