After looking into code of branch-2.1. I found out Driver first handle executor connections by NettyRpcHandler. Once a connection arrive,driver's NettyRpcHandler will call receive,in which NettyRpcHandler#internalReceive will be called. And then NettyEnv#deserialize will be called,which will update NettyRpcEnv.currentClient used for NettyRpcEndpointRef#client. So although rpcaddress is null,the executor;s endpoint ref remained by driver will use the client to send message to executor. Correct me if you found out some other useful message.Thanks!
-- View this message in context: http://apache-spark-developers-list.1001551.n3.nabble.com/Why-Executor-have-no-NettyRpcEndpointRef-tp21432p21506.html Sent from the Apache Spark Developers List mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org