[
https://issues.apache.org/jira/browse/STORM-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109217#comment-14109217
]
ASF GitHub Bot commented on STORM-330:
--------------------------------------
Github user revans2 commented on the pull request:
https://github.com/apache/incubator-storm/pull/220#issuecomment-53281110
I am getting some test failures.
backtype.storm.utils-test test-new-curator-uses-exponential-backoff is
failing with
java.lang.IllegalArgumentException: No matching field found:
getMaxRetryInterval for class
backtype.storm.utils.StormBoundedExponentialBackoffRetry
which is a method you removed.
backtype.storm.messaging.netty-unit-test is getting a divide by zero error
in a lot of the test functions at StormBoundedExponentialBackoffRetry.java:53
> storm.messaging.netty.max_retries option in config file not being used if > 30
> ------------------------------------------------------------------------------
>
> Key: STORM-330
> URL: https://issues.apache.org/jira/browse/STORM-330
> Project: Apache Storm (Incubating)
> Issue Type: Bug
> Affects Versions: 0.9.1-incubating
> Reporter: Roland Jungnickel
> Priority: Minor
>
> I have been trying to set the storm.messaging.netty.max_retries to 240
> because of connection issues when one worker takes a longer time to start its
> processes. But due to this line
> https://github.com/apache/incubator-storm/blob/1a0b46e95ab4ac467525314a75819a75dec92c40/storm-core/src/jvm/backtype/storm/messaging/netty/Client.java#L73
> the max_retries is capped at 30. I am guessing this is a bug or at least
> should be noted somewhere in the documentation?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
