curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From cammckenzie <...@git.apache.org>
Subject [GitHub] curator issue #161: CURATOR-344 - limit shared value watcher to valid change...
Date Wed, 24 Aug 2016 23:28:52 GMT
Github user cammckenzie commented on the issue:

    https://github.com/apache/curator/pull/161
  
    I don't think that this completely fixes the problem. The test fails intermittently because
it's possible that the server gets stopped while the SharedValue is processing the initial
connected event. When this happens, it goes through the retry loop and the assertion at the
end of the test fails.
    
    I think that ultimately the processing that occurs within the watcher's process() method
should be run asynchronously, and equally, the watcher should be more discriminant about which
events it's interested in.
    
    Thoughts?


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message