[
https://issues.apache.org/jira/browse/SPARK-18431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15829642#comment-15829642
]
Sean Owen commented on SPARK-18431:
-----------------------------------
Yeah, it's not a big deal to have an undocumented parameter controlling this,
for advanced users to find. And if it proves something that is commonly and
safely changed to a range of values, it can be promoted to something documented
and supported. But first I think the quesiton is just, does this actually cause
anyone any problem? There are a thousand things that could be configurable and
I suppose we need some basic criteria for making them so.
> Hard coded value in org.apache.spark.streaming.kinesis.KinesisReceiver
> ----------------------------------------------------------------------
>
> Key: SPARK-18431
> URL: https://issues.apache.org/jira/browse/SPARK-18431
> Project: Spark
> Issue Type: Improvement
> Components: DStreams
> Affects Versions: 2.0.1
> Reporter: Shushant Arora
> Priority: Minor
>
> There is a hardcoded value of taskBackoffTimeMillisas 500in onstart method of
> org.apache.spark.streaming.kinesis.KinesisReceiver.Instead of hardcoded value
> it must be configurable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
