Can't switch back to StarterPool

[MartinMason]

Our home region is US Region so...put that out there first. So we're on a purchased capacity and all of it's flaws. One of the issues that we're having is that it is taking 3-4 minutes on average to start up a Spark session. Switched to Small Node Size as we were having lots of trouble even starting a Spark session with the default. Was hoping to switch back to the default to see if the start up time improved after upgrading capacity from F2 to F8. But....can't. Get a toaster message that Spark settings update failed! Can create another Pool and try it but the start up times with any pool other than the StarterPool appears to always be equivalent to spinning up a Databricks cluster.

Any suggestions greatly appreciated.

[MartinMason]

Just tried and it's not fixed yet. But I'm also not seeing Runtime 1.2 as an option so it's likely not deployed to US Central region yet.

[AndyDDC]

Just to add to this, I can't see Runtime 1.2 (UK South).

However, I'm able to switch back and forth between the default StarterPool (Medium) and a new Small pool I created.  I could switch back and forth down to the F2 SKU.  I had thought that possibly F2 wouldn't support a Medium pool.  My thinking is that F2 would only allow 4 cores.  E.G F64 allows 128 Spark V-Cores.

Spark compute for Data Engineering and Data Science - Microsoft Fabric | Microsoft Learn

[Anonymous]

Hi @MartinMason ,

In your case you are not going to see Runtime1.2 as it is not yet deployed to end users. 

But your issue is not related to this deployment, if you are switching back to Starter Pool for any capacity (eg: F2, F4, F8) it should work and you should be able to switch back without any issues.

Incase if you are still facing any issues, can you please share few details of your issue and what you are trying to do with some screenshots. I will try to help to resolve your issue.

Thank you

[Anonymous]

Hi @MartinMason ,

We haven’t heard from you on the last response and was just checking back to see if your query got resolved? Otherwise, will respond back with the more details and we will try to help.

[Anonymous]

Hi @MartinMason ,

We haven’t heard from you on the last response and was just checking back to see if your query got resolved? Otherwise, will respond back with the more details and we will try to help.

[Anonymous]

Hi @MartinMason ,

Thanks for using the Fabric community and reporting this . 

I have reached the internal team for help on this. I will update you once I hear from them.

Appreciate your patience.

[Anonymous]

Hi @MartinMason ,

This error is expected behavior with the existing version on the MS Fabric. The team is working on fixing the issue in upcoming releases and we can expect the fix soon. 

Stay tuned for more updates

[Anonymous]

Hi @MartinMason ,

Apologies for the delay in reply from our side. I have an update from team - the following issue was fixed by the team. Can you please recheck this from your side and confirm us?

Thank you