-
Notifications
You must be signed in to change notification settings - Fork 29k
SPARK-1569 Spark on Yarn, authentication broken by pr299 #649
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
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to exclude null commands altogether? Maybe something like
commands.flatMap(Option(_)), or if that's too much magic,commands.filter(_ != null)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is copy and paste from ClientBase to make the command building be the same, I'd prefer to take any changes to it to a separate jira as I assume there was a reason they didn't do it initially and put a comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note, I can take the changes to make it a list out if you would like and just make that a separate jira, I just ran into the space issue so thought I would make it the same. Really we should perhaps make a utility function for it but we don't have any util classes across client/app master right now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I think we should keep the list, since you don't have to worry about spaces here and there.
For the null thing, I'm trying to understand what it does. If I have a command Seq("java", "null", "-cp", "some.jar", "SomeClass"), doesn't this get compiled to "java null -cp some.jar SomeClass"? It seems that the consequences are undefined if we leave arbitrary "null" strings in there. Also I didn't realize it was copy and pasted from ClientBase, which makes this all the stranger.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, its a bit odd, I just didn't have the time to investigate at this point and figured someone put the comment there perhaps thinking there might be an argument that was "null" was ok. One thing I thought of was if one of the args is null, like the hostname or masterAddress, if you just strip it out, then the usage is wrong and it might not be obvious why its failing. Hopefully it would complain somewhere on startup that a null was passed and it would be easier to debug.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe that --jar is required, but can be "null" (e.g. when using spark-shell or pyspark).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From YarnClientSchedulerBackend.scala::start():
Maybe that explains the need?