[ 
https://issues.apache.org/jira/browse/STORM-1503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15117635#comment-15117635
 ] 

ASF GitHub Bot commented on STORM-1503:
---------------------------------------

GitHub user kishorvpatil opened a pull request:

    https://github.com/apache/storm/pull/1048

    [STORM-1503] Worker should not crash on failure to send heartbeats to 
Pacemaker/ZK

    - Worker should catch and log Exception related to sending worker 
heartbeats to ZK/pacemaker.
    - `PacemakerClient` should not leave open previous channels.. If 
successfully reconnected - made new `Channel`. This avoids worker having unused 
Channel open to Pacemaker around.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kishorvpatil/incubator-storm storm1503

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/storm/pull/1048.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1048
    
----
commit 01116450cfe981fdd37830d7ef2821ea3c0bf99a
Author: Kishor Patil <[email protected]>
Date:   2016-01-22T16:27:46Z

    Pacemaker client must try to reconnect on netty connecton failure

commit b0e696062ec690dc7e279349ce4d0015cd96c08d
Author: Kishor Patil <[email protected]>
Date:   2016-01-26T17:49:11Z

    Worker should retry later instead of dying on failure to send heartbeats to 
ZK/Pacemaker

----


> PacemakerClient Reconnection issue
> ----------------------------------
>
>                 Key: STORM-1503
>                 URL: https://issues.apache.org/jira/browse/STORM-1503
>             Project: Apache Storm
>          Issue Type: Bug
>    Affects Versions: 0.10.0, 0.10.1
>            Reporter: Kishor Patil
>            Assignee: Kishor Patil
>
> Worker should not restart for failure to send heartbeats to Pacemaker or 
> worker.
> Also, PacemakerClient should make reconnect efforts on failure to write on 
> existing channel.



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

Reply via email to