[
https://issues.apache.org/jira/browse/CURATOR-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14942384#comment-14942384
]
ASF GitHub Bot commented on CURATOR-265:
----------------------------------------
GitHub user iocanel opened a pull request:
https://github.com/apache/curator/pull/112
[CURATOR-265] Make sure EnsembleTracker only notifies listeners when …
…the connection string has actually changed. Retry 3 times with a one
second interval in TestReconfiguration.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iocanel/curator curator-265
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/curator/pull/112.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 #112
----
commit bcb8042a40bab51c6ebaa559ed3c88f3e8b4101b
Author: Ioannis Canellos <[email protected]>
Date: 2015-10-03T16:59:50Z
[CURATOR-265] Make sure EnsembleTracker only notifies listeners when the
connection string has actually changed. Retry 3 times with a one second
interval in TestReconfiguration.
----
> Dynamic Reconfig APIs needs some work and more accurate testing
> ---------------------------------------------------------------
>
> Key: CURATOR-265
> URL: https://issues.apache.org/jira/browse/CURATOR-265
> Project: Apache Curator
> Issue Type: Sub-task
> Components: Recipes
> Affects Versions: 3.0.0
> Reporter: Jordan Zimmerman
> Assignee: Jordan Zimmerman
> Fix For: 3.0.0
>
>
> The new dynamic reconfig APIs don't have all permutations and the tests are
> flakey.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
