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

Files in spark_applications_logs are empty #43

Closed
metasim opened this issue Mar 26, 2018 · 2 comments
Closed

Files in spark_applications_logs are empty #43

metasim opened this issue Mar 26, 2018 · 2 comments
Labels
bug closing_soon Wait couple of days for accepting answer

Comments

@metasim
Copy link
Contributor

metasim commented Mar 26, 2018

Seahorse appears to mount spark_applications_logs correctly as many files are created (even .lck files) but all of them have zero bytes. How do we enable logging?

@metasim
Copy link
Contributor Author

metasim commented Mar 26, 2018

FWIW: The impetus for needing these is that we can't connect to an external, stand-alone cluster, and need a means of debugging the problem:

screen shot 2018-03-26 at 5 32 11 pm

@mteldridge
Copy link
Contributor

It looks like the SparkLauncher is not redirecting to the correct session manager logger. Here is a PR for the fix: #49

FYI, the log configuration (https://github.com/deepsense-ai/seahorse/blob/master/seahorse-workflow-executor/commons/src/main/resources/log4j.xml) is creating two appenders. One is the console appender which is what gets redirected in session manager. The other is a rolling file appender that will write to the CWD of the session manager in its Docker container. This might be problematic in that it is an AuFS volume. My recommendation would be to turn off the file appender.

@jaroslaw-osmanski jaroslaw-osmanski added bug closing_soon Wait couple of days for accepting answer labels Apr 13, 2018
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