You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2016/10/25 15:42:58 UTC

[jira] [Resolved] (STORM-2145) Leave leader nimbus's hostname to log when trying to connect leader nimbus

     [ https://issues.apache.org/jira/browse/STORM-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jungtaek Lim resolved STORM-2145.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.3
                   1.1.0
                   2.0.0

Merged into master, 1.x, 1.0.x branches.

> Leave leader nimbus's hostname to log when trying to connect leader nimbus 
> ---------------------------------------------------------------------------
>
>                 Key: STORM-2145
>                 URL: https://issues.apache.org/jira/browse/STORM-2145
>             Project: Apache Storm
>          Issue Type: Improvement
>          Components: storm-core
>            Reporter: Jungtaek Lim
>            Assignee: Jungtaek Lim
>             Fix For: 2.0.0, 1.1.0, 1.0.3
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I have seen lots of question regarding "connection rejected", and most of things are regarding Nimbus H/A, since each Nimbus registers its own hostname and port to Zookeeper, and end-point uses these information to connect to leader Nimbus.
> For now it doesn't leave a log so we can't determine leader Nimbus host unless querying to REST API and see what host name leader Nimbus has. Nimbus H/A configuration is becoming learning curve for Storm 1.x, and it amplifies the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)