[
https://issues.apache.org/jira/browse/KAFKA-3082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15093826#comment-15093826
]
ASF GitHub Bot commented on KAFKA-3082:
---------------------------------------
GitHub user Mszak opened a pull request:
https://github.com/apache/kafka/pull/757
KAFKA-3082: Make LogManager.InitialTaskDelayMs configurable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Mszak/kafka kafka-3082
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/757.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 #757
----
commit 4b6f7b03563f5f80c0f823625b707a21292fb7b0
Author: Jakub Nowak <[email protected]>
Date: 2016-01-12T12:36:56Z
Make LogManager.InitialTaskDelayMs configurable.
----
> Make LogManager.InitialTaskDelayMs configurable
> -----------------------------------------------
>
> Key: KAFKA-3082
> URL: https://issues.apache.org/jira/browse/KAFKA-3082
> Project: Kafka
> Issue Type: Improvement
> Affects Versions: 0.9.0.0
> Reporter: Rado Buransky
> Assignee: Jakub Nowak
> Priority: Minor
>
> At the moment it is hardcoded to 30 seconds which makes it difficult to
> simulate some scenarios for application testing purposes.
> Specifically I am trying to write integration tests for a Spark Streaming
> application to ensure that it behaves correctly even in case when Kafka log
> starts to be cleaned up and I have to wait 30 seconds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
