In this blog post, we will explain how to get more insight into weird azure storage emulator problems.
Recently, I encountered an issue where doing
GET requests against Table Storage in the Azure storage emulator was working but
PUT requests were failing with a generic
500 coming back from the emulator.
I’ve had these kinds of issues in the past with a mismatch between the azure storage dlls and the emulator version but in this case, nothing had changed from “it worked fine last time I did this” to “why is this broken now?”
Spoiler alert: the problem was that the SQL data file (.mdf) backing the emulator was full… yeah, I know, I’m that lucky ;)
In the exception I was receiving in Visual Studio, I was seeing a request ID in the form of a guid. That lead me to think about looking into logs. Ok, I googled first and most of the solutions involved resetting the db backing azure table storage which I didn’t want to do right away… though that would have solved my issue, as you will figure out later.
So, I did find this great blog post back from 2013 (or 5 lifetimes ago in software development years) explaining how to turn on logs in azure storage emulator. Being that ‘old’, things have changed a little bit.
To enable logs:
- Navigate to
- Locate the
.configmatching your version of the emulator. In my case it was
- Restart Storage Emulator (very important)
- At the same time, you can see where the logs will be written under the
it should look something like this:
<?xml version="1.0"?> <StorageEmulator xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SQLInstance>(localdb)\MSSQLLocalDB</SQLInstance> <PageBlobRoot>C:\Users\olivierv\AppData\Local\AzureStorageEmulator\PageBlobRoot</PageBlobRoot> <BlockBlobRoot>C:\Users\olivierv\AppData\Local\AzureStorageEmulator\BlockBlobRoot</BlockBlobRoot> <LogPath>C:\Users\olivierv\AppData\Local\AzureStorageEmulator\Logs</LogPath> <LoggingEnabled>true</LoggingEnabled> </StorageEmulator>
Now on to my specific issue
Navigating to the logs folder, I found a set of files. I then just opened the first one and right there in the first paragraph was:
The fatal unexpected exception ‘The fatal unexpected exception ‘Could not allocate space for object ‘dbo.TableRow’.’PK_dbo.TableRow’ in database ‘AzureStorageEmulatorDb52’ because the ‘PRIMARY’ filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.’
Oh, isn’t that interesting.
I knew that Azure Storage Emulator was using
SQL LocalDb has its storage engine.
So, I went and had a look at
%userprofile% and to my surprise the file
AzureStorageEmulatorDb52.mdf was 10 Gb big.
Digging even deeper: why is the .mdf file 10 Gb big?
So, I connected to the SQL
LocalDb instance using Visual Studio Sql Explorer view and issued this query to find where all these bytes were having a party.
TableRow table (which holds records for table storage) was using almost all of the 10 Gb.
I then found out that 99%+ of those records where from an azure table storage table named
It turns out I had an old cloud service running on my box set up to collect machine level metrics (cpu, memory, etc), which was dumping into the emulator and filled it up.
I deleted those rows and everything started to work normally :D
Hope it helps someone.
Subscribe via RSS