GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/16380
[SPARK-18972][Core]Fix the netty thread names for RPC
## What changes were proposed in this pull request?
Right now the name of threads created by Netty for Spark RPC are
`shuffle-client-**` and `shuffle-server-**`. It's pretty confusing.
This PR just uses the module name in TransportConf to set the thread name.
In addition, it also includes the following minor fixes:
- TransportChannelHandler.channelActive and channelInactive should call the
corresponding super methods.
- Make ShuffleBlockFetcherIterator throw NoSuchElementException if it has
no more elements. Otherwise, if the caller calls `next` without `hasNext`, it
will just hang.
## How was this patch tested?
Jenkins
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zsxwing/spark SPARK-18972
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/16380.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #16380
----
commit 5b51040c8b7aa5fc0c24d765814ec0670f200442
Author: Shixiong Zhu <[email protected]>
Date: 2016-12-21T22:52:57Z
Fix the netty thread names for RPC
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
