Spark UI fixes for WebUI-Executors - "Request is a replay (34) attack" #7
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See: https://issues.apache.org/jira/browse/SPARK-21487
I identified a bug on spark 3, when connecting to the Spark UI through RM proxy, executors tab is not rendered.
if i recall correctly it is fixed in hadoop 3.3, I couldnt find my source so might need a test.
The fix only consists of renaming .html files to .mustache files. HTML files are being filtered by an authentication filter in the YARN RM proxy, changing its behaviour and asking for a new request. Kerberos does not like that and raises an error.
Modifying file extension to .mustaches fixes the issue