Forum Discussion
Slow starter pool session initialization
I am currently experimenting with a F2 capacity. Whenever I try to run a notebook it takes somewhere between 2 and 2.5 minutes to start the spark cluster even though I'm using the starter pool. All settings related to Spark are left as default for the workspace. Tried both running things manually as well as triggering the notebook from data factory.
If I go into a trial workspace and run a notebook the spark session is started in just a few seconds. This makes me think that it might be a limitation depending on which capacity you are using? But the documentation gives no indication of this: https://learn.microsoft.com/en-us/fabric/data-engineering/spark-compute
23 Replies
I have unmarked previous reply as solution. For me, the main issue here is that we have no proper way of tracking these type of issues. I have reported multiple issues that have been confirmed by a Microsoft but nothing is added to the known issues page: https://support.fabric.microsoft.com/en-us/known-issues - as the page is not updated we cannot really know if the issue has been acknowledged. The page also gives a false impression of few or no issues in Fabric. It is difficult to maintain credibility towards our customers when we don't have transparency from Microsoft.
Agreed! A Microsoft support engineer told me last week that an issue was in their internal known issues tracker, but that it would not be added to the public known issues page. Very frustrating.
It is getting worst for me, sometimes it just fails after a long time of trying to start.
Hi Anonymous ,
Apologies for the issue you have been facing. We have an update from the team.
We got impacted by this limitation on supporting 1 node starter pools mainly for F2 capacity sku. Team have added this to Known Issues section in the document and the latest version should be published end of this week. We are working on a fix to enable 5 second session start experience for F2 capacity. I will update this thread once the fix is rolled out in few weeks.
Thank youThis should not be an accepted solution. The issue is still there. I'm on a F4 and facing 2+ minutes startup time.
