GitHub user cnZach opened a pull request:
https://github.com/apache/spark/pull/16412
[SPARK-19006][DOCS]mention spark.kryoserializer.buffer.max must be less
than 2048m in doc
## What changes were proposed in this pull request?
On configuration doc
page:https://spark.apache.org/docs/latest/configuration.html
We mentioned spark.kryoserializer.buffer.max : Maximum allowable size of
Kryo serialization buffer. This must be larger than any object you attempt to
serialize. Increase this if you get a "buffer limit exceeded" exception inside
Kryo.
from source code, it has hard coded upper limit :
```
val maxBufferSizeMb = conf.getSizeAsMb("spark.kryoserializer.buffer.max",
"64m").toInt
if (maxBufferSizeMb >= ByteUnit.GiB.toMiB(2))
{ throw new IllegalArgumentException("spark.kryoserializer.buffer.max must
be less than " + s"2048 mb, got: + $maxBufferSizeMb mb.") }
```
We should mention "this value must be less than 2048 mb" on the
configuration doc page as well.
## How was this patch tested?
None. Since it's minor doc change.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cnZach/spark SPARK-19006
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/16412.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 #16412
----
commit ca3e142199e0aa42ce12241987e3f653868c2f85
Author: Yuexin Zhang <[email protected]>
Date: 2016-12-27T01:21:36Z
mention spark.kryoserializer.buffer.max must be less than 2048m
----
---
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]
