Forum Discussion
Scaling up to down fabric capacity giving utilisation error.
Hello,
I have upscale my fabric capacity to F32 from F8 because I want to process 400 gb of data so now I have completed my work on few minutes and then I have down scale fabric capacity from F32 to F8 but after scaling down it is giving error like your organization has used entire capacity no capacity available. How to resolve this i don't want to increase capacity to resolve this issue.
Hi ankitmori91, With the way background operations work in Fabric, it is smoothed over a 24 hour window, so a copy job that jumps your capacity up to 50% and runs for one hour is actually jumping your capacity up to 1200% but it is smoothed over 24 hours so it only appears as 50% for 24 hours.
Until the background operation smoothing is done, it is not safe to resize your capacity. you're not being charged extra, you're just being charged what it costs.
What you can do is pause the capacity and resume it to remove the smoothing, but then you will be hit with a bill for the compute that you used and didn't smooth out.
7 Replies
- tayloramy
Super User
Hi ankitmori91,
Take a look at the Capacity Metrics app to see what your overall usage is.
This is likely related to smoothing, when you scaled up to F32, you did a bunch of data loading, which is classified as a background operation. Background operations are smoothed over a 24 hour window, so you should keep the F32 for 24 hours after your loads have finished, then once you see capacity usage go back to normal, it is safe to scale back down.
Hello tayloramy,
Thank you for your prompt support, but don't you think it is bottle neck because if we need capacity for 2 hours it be applicable for that duration only else it will end up charging us extra cost. Is the any settings at tenant level or workspace level to achieve it.
- tayloramy
Hi ankitmori91, With the way background operations work in Fabric, it is smoothed over a 24 hour window, so a copy job that jumps your capacity up to 50% and runs for one hour is actually jumping your capacity up to 1200% but it is smoothed over 24 hours so it only appears as 50% for 24 hours.
Until the background operation smoothing is done, it is not safe to resize your capacity. you're not being charged extra, you're just being charged what it costs.
What you can do is pause the capacity and resume it to remove the smoothing, but then you will be hit with a bill for the compute that you used and didn't smooth out.
Murtaza_Ghafoor@ankitmori91
Scaling down from f32 to f8 immediatley does not means that your capacity is not throttled. If you have fabric capacity metrics app installed, please check from In Fabric Capacity Metrics, check:- CU consumption
- CU utilization %
- Throttling
- Background vs Interactive operations
- Which workload/item is consuming the capacity
If you see 100% operations or throttling, wait for the existing workload to finish before starting another large operation.
If this helps, ✓ Mark as Kudos | Help Others
- GilbertQ
Hi ankitmori91
If you're bringing in data using notebooks, what you can do instead is use the Spark auto scale option which will not affect your capacity and you will simply be charged for the man to spark that you are using. There are more details.
https://community.fabric.microsoft.com/discussions/ac_dataengineering/scaling-up-to-down-fabric-capacity-giving-utilisation-error-/5359896
- Kagiyama_yutaka
Continued Contributor
Could you add a little more detail after you scaled down from F32 to F8? Please tell what workload you used for the 400GB processing and what the Capacity Metrics App shows for background CU and throttling.
v-kathullacCommunity Support
Thankyou Kagiyama_yutaka , GilbertQ , Murtaza_Ghafoor , tayloramy for Addressing the issue.
Hi Chetan40 ,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided for the issue worked? or Let us know if you need any further assistance?
Regards,
Chaithanya
