You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@curator.apache.org by "Jordan Zimmerman (Jira)" <ji...@apache.org> on 2020/04/11 15:04:00 UTC

[jira] [Created] (CURATOR-566) Re-assess tech debt in Connection Handling

Jordan Zimmerman created CURATOR-566:
----------------------------------------

             Summary: Re-assess tech debt in Connection Handling
                 Key: CURATOR-566
                 URL: https://issues.apache.org/jira/browse/CURATOR-566
             Project: Apache Curator
          Issue Type: Improvement
          Components: Client, Framework
    Affects Versions: 4.3.0
            Reporter: Jordan Zimmerman


As seen in CURATOR-525, there is a lot of tech debt and, frankly, incomprehensible code in parts of Curator's connection handling. CURATOR-525 had to add an ugly hack due to races between ZooKeeper's watcher thread and Curator's connection state setting thread. 

Consider, reworking or rewriting the connection handling in Curator.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)