Github user jinxing64 commented on a diff in the pull request:
https://github.com/apache/spark/pull/18388#discussion_r128498015
--- Diff:
common/network-common/src/main/java/org/apache/spark/network/util/TransportConf.java
---
@@ -257,4 +257,7 @@ public Properties cryptoConf() {
return CryptoUtils.toCryptoConf("spark.network.crypto.config.",
conf.getAll());
}
+ public long maxChunksBeingTransferred() {
+ return conf.getLong("spark.network.shuffle.maxChunksBeingTransferred",
Long.MAX_VALUE);
--- End diff --
It depends on memory config of NodeManager. In our cluster, we will set it
to be 3G(memory overhead for Netty)/1k(size of
ChannelOutboundBuffer$Entry)=3000000.
I think it's ok to leave it MAX_VALUE(by default it's disabled).
---
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]
