[
https://issues.apache.org/jira/browse/STORM-1106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957917#comment-14957917
]
ASF GitHub Bot commented on STORM-1106:
---------------------------------------
Github user HeartSaVioR commented on the pull request:
https://github.com/apache/storm/pull/795#issuecomment-148217847
Seems like default value of storm.messaging.netty.max_wait_ms is very small.
I didn't see the details about StormBoundedExponentialBackoffRetry, but if
it is running as intended via class comment, we're sleeping between 100 ~ 1000
ms for each retry by default.
But we're pinning max retry count to 29 from
ExponentialBackoffRetry.validateMaxRetries() since we use 1 << retryCount to
sleep, resulting that we only sleep about max 29 secs, which is too short.
> Netty Client Connection Attempts should not be limited
> ------------------------------------------------------
>
> Key: STORM-1106
> URL: https://issues.apache.org/jira/browse/STORM-1106
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-core
> Affects Versions: 0.10.0
> Reporter: Kishor Patil
> Assignee: Kishor Patil
> Priority: Blocker
>
> The workers should not give-up making connection with other workers. This
> could cause the worker to be blocked forever.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
