[
https://issues.apache.org/jira/browse/STORM-2773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla closed STORM-2773.
----------------------------------
Resolution: Won't Fix
We are currently cleaning up old issues with stale discussions. The last
comment here was made 5 years ago and Storm as evolved. If this is still an
issue or relevant for your work, feel free to re-open and to rebase / fix the
related PR.
> If a drpcserver node in cluster is down,drpc cluster won't work if we don't
> modify the drpc.server configuration and restart the cluster
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: STORM-2773
> URL: https://issues.apache.org/jira/browse/STORM-2773
> Project: Apache Storm
> Issue Type: Bug
> Components: storm-client
> Affects Versions: 2.0.0
> Reporter: liuzhaokun
> Assignee: liuzhaokun
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> There is a cluster which includes three nodes named storm1,storm2,storm3.And
> there is a drpcserver in every node,a worker which has been started on
> strom1.When strom1 was down with hardware failure,my drpc topology won't
> work,when I send request from drpcclient.
> As storm1 was down,so the worker will be restarted on another node,but it
> can't Initialize successfully because the call method of Adder will throw a
> RuntimeException,when drpcspout try to connect to storm1,so the worker will
> restart again.
> In conclusion,If a drpcserver node in cluster is down,drpc cluster won't work
> until we modify the drpc.server configuration and restart the cluster,but in
> production,it's difficult to restart whole cluster.
> So I think we should catch the RuntimeException and log it,and the drpc
> topology will work normally.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
