Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/9285#discussion_r43079451
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/util/WriteAheadLogUtils.scala
---
@@ -39,6 +39,7 @@ private[streaming] object WriteAheadLogUtils extends
Logging {
val DEFAULT_ROLLING_INTERVAL_SECS = 60
val DEFAULT_MAX_FAILURES = 3
+ val WAL_CLOSE_AFTER_WRITE =
"spark.streaming.writeAheadLog.closeAfterWrite"
--- End diff --
Take a look at how rollingIntervalSecs is implemented. That also has
separate configurations for driver and receiver
On Mon, Oct 26, 2015 at 7:47 PM, Burak Yavuz <[email protected]>
wrote:
> In
>
streaming/src/main/scala/org/apache/spark/streaming/util/WriteAheadLogUtils.scala
> <https://github.com/apache/spark/pull/9285#discussion_r43079268>:
>
> > @@ -39,6 +39,7 @@ private[streaming] object WriteAheadLogUtils extends
Logging {
> >
> > val DEFAULT_ROLLING_INTERVAL_SECS = 60
> > val DEFAULT_MAX_FAILURES = 3
> > + val WAL_CLOSE_AFTER_WRITE =
"spark.streaming.writeAheadLog.closeAfterWrite"
>
> @tdas <https://github.com/tdas> Noticed that this is going to be super
> hard. How are we going to differentiate between a receiver WAL and a
driver
> WAL in the write method of FileBasedWAL?
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/9285/files#r43079268>.
>
---
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]
