Forum Discussion
Lakehouse high CU usage, unknown source
Support finally got back to me with this reply. They admitted to it being a backend Microsoft issue, but no word on how and if they would be fixing it or if I would be reinbursed the lost CU's. The abbreviated 'DMS' is for Data Movement Services:
The increased CU usage was attributed to a disabled file system (FS) on the DMS side, which resulted in a significant number of “GetBlobProperties” API calls from DMS to the One Lake Client (OLC). This led to the observed spike in CU usage. After the FS was re-enabled on July 29th, CU usage decreased accordingly.
The spike occurred on 07/18 and subsided on 07/29, aligning with the period when the FS was disabled and subsequently re-enabled on the DMS side, which reduced the number of calls from DMS to OLC.
No support has still not resolved it.
We keep hitting 100% usage now to the point I cant really get any work done. Its a bad situation to say the least, we have hard deadlines for our project, we are paying for a service we cannot use, I am NOT happy right now.
Last night I deleted 2 Lakehouses that contained the most data to try and get some available CU's, but even that seemed not to help as an hour later I was still getting 100% CU usage emails. I paused the Capacity for 3 hours and enabled again last night and am now looking to see what the effect is.
To see how REDICULOUS this is have a look at my metrics chart. When I looked at it I thought they had lost my data, then I noticed the Y axis values: