Randomly cannot "acquire exclusive access to dataset" when using the Rest API

[kri_ostlund]

We are working on a real time dashboard where my team and I have chosen to push data using the Rest API (as opposed to using Streaming Analyitcs), as this gives us the ability reset the data at any given time as we've found no other way of displaying today's and this week's data in the Service. We push data at most every 10 seconds, and clear the datasets either dayly or weekly depending on what data they hold.

Now, when either pushing new rows, or clearing datasets, we randomly return error messages saying "Acquiring exclusive access to dataset <dataset_id> timed out. Please try again later.".  Is this a fault on our side, or is it something with Power BI? Has anyone else had this issue?

I've been in contact with Microsoft on multiple occasions, but every time, the service (and API) seems to have been working as expected. So there hasn't been much to discuss there.

Sidenote: 

I've chosen to put this under Developer instead of under Service as this is presumably more about the Rest API than Service. I'm happy to repost this in Service if that's a more suitable forum.

[bsjut]

We've started seeing this today, as well. Interesting ly, also the frontend is then unable to access the dataset anymore. It just displays an error level. To me it looks like a data integrity issue on the data model side? 

[bsjut]

This is happening as of today again; The affected dataset is 

213d2dfb-1ed9-420a-96e5-a9a6ea1239d8

If anybody from Microsoft reading this: Can you comment if this is a know issue? The rest API is firing 500 errors 

[bsjut]

@jocaplan-MSFT, do you know who would be the right person to escalate this to? 

[jocaplan-MSFT]

Please open a support ticket. I'll check around in the mean-time

[bsjut]

Thanks for looking into this. This appears fairly randomly every other week. To me it looks like a bug on the API side, as it's undocumented behavior

[bsjut]

This is happening again, as of right now,

• I2016-09-07T12:15:40.163Z]{"uuid":"58a549f5-42cb-f3a2-de92-27e42c608d59","status":500,"headers":{"Cache-Control":"no-store, must-revalidate, no-cache","Connection":"close","Content-Type":"application/json; charset=utf-8","Date":"Wed, 07 Sep 2016 12:15:40 GMT","RequestId":"434435ac-6567-4f49-bdca-4a68e0f9b8b3","Server":"Microsoft-HTTPAPI/2.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0","Strict-Transport-Security":"max-age=31536000; includeSubDomains","X-Content-Type-Options":"nosniff","X-Frame-Options":"deny"},"text":"{\"error\":{\"code\":\"GeneralException\",\"message\":\"Acquiring exclusive access to dataset 213d2dfb-1ed9-420a-96e5-a9a6ea1239d8 timed out. Please try again later. \"}}","data":{"error":{"code":"GeneralException","message":"Acquiring exclusive access to dataset 213d2dfb-1ed9-420a-96e5-a9a6ea1239d8 timed out. Please try again later. "}},"buffer":[123,34,101,114,114,111,114,34,58,123,34,99,111,100,101,34,58,34,71,101,110,101,114,97,108,69,120,99,101,112,116,105,111,110,34,44,34,109... (truncated)

[bsjut]

We see this happening again today, since a few hours. It's really hard to believe that we're the only ones affected. 

[bsjut]

.. and it's happening again today.

[jocaplan-MSFT]

Looks like you are using an older implementation of our dataset API. Your dataset should automatically be upgraded in the next few weeks. Recreating the dataset would also recreate it on our new stack.

[bsjut]

ah, thanks for the reply. We'll wait it out, I guess. We couldn't stream back the data to that data set, it's not logged on our side forever.