-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-6716] Change SparkContext.DRIVER_IDENTIFIER from <driver> to driver #5372
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
Conversation
|
/cc @marmbrus @jerryshao |
|
Test build #29732 has started for PR 5372 at commit |
|
Test build #29732 has finished for PR 5372 at commit
|
|
Test PASSed. |
|
Do we need to modify |
|
Good call; I'll update |
|
Test build #29734 has started for PR 5372 at commit |
|
Test build #29734 has finished for PR 5372 at commit
|
|
Test PASSed. |
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 could be interpreted as implying it is only needed for tests, however, this is actually legitimately needed for reading old event logs. It might make more sense to just say it's needed for backwards compatibility.
|
Left a very minor comment but otherwise LGTM |
|
Test build #29742 has started for PR 5372 at commit |
|
Test build #29742 has finished for PR 5372 at commit
|
|
Test PASSed. |
|
Good call on the original comment wording being potentially confusing. I've updated this as suggested. I'm going to merge this into |
Currently, the driver's executorId is set to
<driver>. This choice of ID was present in older Spark versions, but it has started to cause problems now that executorIds are used in more contexts, such as Ganglia metric names or driver thread-dump links the web UI. The angle brackets must be escaped when embedding this ID in XML or as part of URLs and this has led to multiple problems:The simplest solution seems to be to change this id to something that does not contain any special characters, such as
driver.I'm not sure whether we can perform this change in a patch release, since this ID may be considered a stable API by metrics users, but it's probably okay to do this in a major release as long as we document it in the release notes.