Forum Discussion
Notebook Activity Stuck At Running Cell
Been experiencing this issue only recently where my notebook runs forever without progressing from a cell. When I check the log, the below is shown:
The log just keeps refreshing itself along those lines and nothing moves. This has occured multiple times. Sometimes before running any code in a cell, and others when it's halfway through. Tried restarting the notebook but that has only worked a few times as the problem comes back at random (yes, not the same cell that's causing this each time). It's like Pyspark just decides to stop working but I don't know what's causing it and hence unable to recitfy the issue.
Has anyone else experienced the same?
8 Replies
- AnonymousNot applicable
Hi scca ,
Apologies for the issue you are facing.
At this time, we are reaching out to the internal team to get some help on this .
We will update you once we hear back from them.- AnonymousNot applicable
Hi scca ,
Apologize for the issue you are facing. The best course of action is to open a support ticket and have our support team take a closer look at it.
Please reach out to our support team so they can do a more thorough investigation on why this it is happening: Link
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
Hope this helps. Please let us know if you have any other queries.
- AnonymousNot applicable
Hi scca ,
We haven’t heard from you on the last response and was just checking back to see if you got a chance to create support ticket.
After creating a Support ticket please provide the ticket number as it would help us to track for more information.
- AnonymousNot applicable
Having the same problem, after numerus refreshes, I see a cursor labeld with my own name as if I were collaborating with somebody. and I can't join a spark session anymore. but only that notebook, saving to a different name works. will try tomorrow again.
- zzthatcherAdvocate I
I get this issue frequently as well. It usually happens when I am using temporary directories. Is that the case with you as well?
- sccaAdvocate III
Are you referring to the original issue I posted? If yes, then I no longer face this issue, at least not according to my regular job runs nowadays. As for my case, when it occurred, there wasn't any temporary directories involved.