You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/10/22 21:04:27 UTC

[jira] [Commented] (STORM-1125) Separate ZK Write Client for Nimbus

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

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

GitHub user kishorvpatil opened a pull request:

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

    [STORM-1125] Adding separate ZK client for read in Nimbus ZK State

    Separate reader and writer for nimbus to avoid longer waits for reads to finish.

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

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

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

    https://github.com/apache/storm/pull/813.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 #813
    
----
commit 0726ef00ec68f88ac6deccb6d3950c0d4805de6a
Author: Kishor Patil <kp...@yahoo-inc.com>
Date:   2015-10-22T18:51:53Z

    Adding separate ZK client for read in Nimbus ZK State

----


> Separate ZK Write Client for Nimbus
> -----------------------------------
>
>                 Key: STORM-1125
>                 URL: https://issues.apache.org/jira/browse/STORM-1125
>             Project: Apache Storm
>          Issue Type: Improvement
>            Reporter: Kishor Patil
>            Assignee: Kishor Patil
>
> Given the amount of reads from ZK by nimbus, shared ZK connections for write quickly starts overwhelm single connection blocking writes without any dependence.



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