[SPARK-21701][CORE] Enable RPC client to use SO_RCVBUF, SO_SNDBUF and SO_BACKLOG in SparkConf #18922
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
TCP parameters like SO_RCVBUF, SO_SNDBUF and SO_BACKLOG can be set in
SparkConf
, andorg.apache.spark.network.server.TransportServer
can use those parameters to build server by leveraging netty. But forTransportClientFactory
, there is no such way to set those parameters fromSparkConf
. This could be inconsistent in server and client side when people set parameters inSparkConf
. So this PR make RPC client to be enable to use those TCP parameters as well.Add some comments to
MessageDecoder
class to show how wire format looks like for a RPC message and draw a vivid graph to present to detailed wire protocol.How was this patch tested?
Existing tests and refine asking non-existent endpoint test case in
RpcEnvSuite
.