-
Notifications
You must be signed in to change notification settings - Fork 28.9k
[SPARK-12101][Core]Fix thread pools that cannot cache tasks in Worker and AppClient #10108
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
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.
The previous codes are right. Just use newDaemonCachedThreadPool to make codes simple.
|
This should be attached to SPARK-11999 right? |
RC1 is coming out, so I created a new ticket. |
|
Hm, what do you mean? no RC has been announced |
|
RC1 is cut. See bf52584 |
|
@pwendell this should probably be announced on the list when you start or else we might have a very small chance of a race condition in tagging/merging things. I get the point that your first half of the fix could conceivably end up in 1.6.0 and not the other, but is that a good thing? you made a second JIRA anyway I see, so one of them needs to be associated here. I think we have a larger problem, as ever in Spark, if people are just merging fixes right up to and well past the deadline. We were supposed to be cutting RCs 3 weeks ago, but it arbitrarily happened now. |
|
BTW @srowen, some protocol for announcing these is probably a good idea to avoid races. I think we haven't suffered from races in the past, but mostly out of luck. |
Oops. Sorry. Forgot to add the JIRA number to the title. |
|
Sorry if this seemed arbitrary, I cut the release as soon as all the blocker issues were resolved. In the future I'll announce on the dev list first. |
|
Test build #47079 has finished for PR 10108 at commit
|
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.
the #%d doesn't do anything here right? We don't call format on this string
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.
actually, this is setting a format so it does do something. Maybe we should add it back in the new code
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.
ThreadUtils.namedThreadFactory will do the similar thing except the format is -%d. I think it's better to make all threads have the same format in Spark.
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.
oh I see, it's a prefix that we're passing in here
|
This patch itself looks good pending 1 minor comment. |
|
Merging into master 1.6 |
…r and AppClient `SynchronousQueue` cannot cache any task. This issue is similar to #9978. It's an easy fix. Just use the fixed `ThreadUtils.newDaemonCachedThreadPool`. Author: Shixiong Zhu <[email protected]> Closes #10108 from zsxwing/fix-threadpool. (cherry picked from commit 649be4f) Signed-off-by: Shixiong Zhu <[email protected]>
…r and AppClient (backport 1.5) backport #10108 to branch 1.5 Author: Shixiong Zhu <[email protected]> Closes #10135 from zsxwing/fix-threadpool-1.5.
SynchronousQueuecannot cache any task. This issue is similar to #9978. It's an easy fix. Just use the fixedThreadUtils.newDaemonCachedThreadPool.