-
Notifications
You must be signed in to change notification settings - Fork 28k
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
[SPARK-11996][Core]Make the executor thread dump work again #9976
Conversation
In the previous implementation, the driver needs to know the executor listening address to send the thread dump request. However, in Netty RPC, the executor doesn't listen to any port, and the executor thread dump feature is broken. This patch makes the driver use the endpointRef stored in BlockManagerMasterEndpoint to send the thread dump request to fix it.
/cc @vanzin |
Test build #46703 has finished for PR 9976 at commit
|
import org.apache.spark.rpc.{ThreadSafeRpcEndpoint, RpcEnv, RpcCallContext, RpcEndpoint} | ||
import org.apache.spark.util.ThreadUtils | ||
import org.apache.spark.rpc.{RpcCallContext, RpcEnv, ThreadSafeRpcEndpoint} | ||
import org.apache.spark.util.{Utils, ThreadUtils} |
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.
super nit: order.
LGTM. |
Test build #46706 has finished for PR 9976 at commit
|
Test build #46712 has finished for PR 9976 at commit
|
retest this please |
Test build #46734 has finished for PR 9976 at commit
|
retest this please |
Test build #46746 has finished for PR 9976 at commit
|
Test build #2118 has finished for PR 9976 at commit
|
retest this please |
Test build #46776 has finished for PR 9976 at commit
|
Not sure why this happens frequently. I saw some weird logs in the build:
Just several seconds for the tests but the total time was 18 minutes. Is this because the global ivy lock, such as, other build in the same machine took a lot of time to resolve the dependencies? |
retest this please |
Test build #46786 has finished for PR 9976 at commit
|
I'm going to merge this. |
In the previous implementation, the driver needs to know the executor listening address to send the thread dump request. However, in Netty RPC, the executor doesn't listen to any port, so the executor thread dump feature is broken. This patch makes the driver use the endpointRef stored in BlockManagerMasterEndpoint to send the thread dump request to fix it. Author: Shixiong Zhu <shixiong@databricks.com> Closes #9976 from zsxwing/executor-thread-dump. (cherry picked from commit 0c1e72e) Signed-off-by: Reynold Xin <rxin@databricks.com>
In the previous implementation, the driver needs to know the executor listening address to send the thread dump request. However, in Netty RPC, the executor doesn't listen to any port, so the executor thread dump feature is broken.
This patch makes the driver use the endpointRef stored in BlockManagerMasterEndpoint to send the thread dump request to fix it.