Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/9734#discussion_r44907725
--- Diff: docs/streaming-programming-guide.md ---
@@ -2001,8 +2001,7 @@ If the number of tasks launched per second is high
(say, 50 or more per second),
of sending out tasks to the slaves may be significant and will make it
hard to achieve sub-second
latencies. The overhead can be reduced by the following changes:
-* **Task Serialization**: Using Kryo serialization for serializing tasks
can reduce the task
- sizes, and therefore reduce the time taken to send them to the slaves.
+* **Task Serialization**: Using Kryo serialization for serializing tasks
can reduce the task sizes, and therefore reduce the time taken to send them to
the slaves. This is controlled by the spark.closure.serializer property.
However, at this time, Kryo serialization cannot be enabled for closure
serialization. This may be resolved in a future release.
--- End diff --
Let's see if others have comments about the text. Note you should
back-tick-quote the `spark.closure.serializer` property.
---
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]
