-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-21494][network] Use correct app id when authenticating to external service. #18706
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -243,7 +243,6 @@ public void initializeApplication(ApplicationInitializationContext context) { | |
| String appId = context.getApplicationId().toString(); | ||
| try { | ||
| ByteBuffer shuffleSecret = context.getApplicationDataForService(); | ||
| logger.info("Initializing application {}", appId); | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think this is to verbose personally. We do log when initializeContainer so I guess its ok to remove this. But if you remove this I think we should remove the one in stopApplication as well since they go hand in hand.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I rebuilt my cluster this morning so I don't have the logs anymore... but what I noticed is that this callback gets called multiple times (once per container belonging to the app), while I only remember the stop callback being called when the application actually stops. So it didn't seem like the behavior was as symmetric as one would expect. But the secret manager also prints an info message on unregistration, so I guess the important things are still logged even if these two messages are removed.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yep, here's an edited portion of the log (without this patch, so notice the duplicate registration messages too): |
||
| if (isAuthenticationEnabled()) { | ||
| AppId fullId = new AppId(appId); | ||
| if (db != null) { | ||
|
|
@@ -262,7 +261,6 @@ public void initializeApplication(ApplicationInitializationContext context) { | |
| public void stopApplication(ApplicationTerminationContext context) { | ||
| String appId = context.getApplicationId().toString(); | ||
| try { | ||
| logger.info("Stopping application {}", appId); | ||
| if (isAuthenticationEnabled()) { | ||
| AppId fullId = new AppId(appId); | ||
| if (db != 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.
Hah, this is actually fixing a memory leak...