You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/05 04:12:27 UTC
[jira] [Updated] (STORM-330) storm.messaging.netty.max_retries
option in config file not being used if > 30
[ https://issues.apache.org/jira/browse/STORM-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Kellogg updated STORM-330:
-------------------------------
Component/s: storm-core
> 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
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 0.9.1-incubating
> Reporter: Roland Jungnickel
> Assignee: Kishor Patil
> Priority: Minor
> Fix For: 0.9.3
>
>
> 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.3.4#6332)