Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/18388#discussion_r128878335
--- 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 --
This default value totally depends on the JVM heap size. Seems hard to pick
up a reasonable value. If it's too small, then if a user uses a large heap
size, when they upgrade, their shuffle service may start to fail. If it's too
large, it's just the same as MAX_VALUE.
---
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]
