GitHub user srdo opened a pull request:

    https://github.com/apache/curator/pull/216

    CURATOR-402: Curator should not use QuorumServer.addr when updating the 
connect string dynamically

    …e the client connect string, resulting in a client unable to reconnect
    
    See https://issues.apache.org/jira/browse/CURATOR-402.
    
    I took a look at adding a test for this, but both addresses are null when 
using a single testing server, and I couldn't find a way to start a testing 
cluster where clientAddr is null.

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

    $ git pull https://github.com/srdo/curator CURATOR-402

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

    https://github.com/apache/curator/pull/216.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 #216
    
----
commit 942b96368dbd536a61c5cb150bd081a6f0ac2754
Author: Stig Rohde Døssing <[email protected]>
Date:   2017-04-24T18:23:41Z

    Fix EnsembleTracker sometimes using the Zookeeper peer ports to update the 
client connect string, resulting in a client unable to reconnect

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to