Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Python Notebook node nonfunctional #45

Closed
bguseman opened this issue Mar 29, 2018 · 5 comments
Closed

Python Notebook node nonfunctional #45

bguseman opened this issue Mar 29, 2018 · 5 comments
Labels
bug closing_soon Wait couple of days for accepting answer

Comments

@bguseman
Copy link

bguseman commented Mar 29, 2018

Using a workflow with a 'Read DataFrame' node (which runs successfully) connected directly to a 'Python Notebook' node, the Python Notebook is completely nonfunctional under the Pyspark kernel. The notebook is accessible, but the Pyspark kernel looks like it is constantly busy, and attempting to run a code cell does nothing. Restarting the kernel also fails.

Please see the included log snippets. The jupyter log came from inside the running notebooks container. The console log and the headless jupyter snippet were written to the startup console.

I am running on a Mac

console.log
jupyter_headless.log
jupyter.log

@metasim
Copy link
Contributor

metasim commented Apr 10, 2018

@jaroslaw-osmanski Any direction on how we might further debug/address this is really appreciated. This is a major blocker for us right now, and we're out of ideas on how to isolate the problem.

@jaroslaw-osmanski
Copy link

#51 should solve it.
Quick fix: downgrade tornado to 4.1 on sessionmanager container.

@jaroslaw-osmanski
Copy link

@bguseman @metasim Can you confirm that it is solved in master?

@jaroslaw-osmanski jaroslaw-osmanski added the closing_soon Wait couple of days for accepting answer label Apr 13, 2018
@metasim
Copy link
Contributor

metasim commented Apr 13, 2018

@jaroslaw-osmanski We'll test it today or Monday. Been at a conference.

@metasim
Copy link
Contributor

metasim commented Apr 13, 2018

@jaroslaw-osmanski I can confirm that this is now working after a fresh build. Thanks so much for addressing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug closing_soon Wait couple of days for accepting answer
Projects
None yet
Development

No branches or pull requests

3 participants