You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Mike Drob (Jira)" <ji...@apache.org> on 2022/05/16 14:51:00 UTC

[jira] [Commented] (ZOOKEEPER-4519) Testable interface should have a testableCloseSocket() method

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

Mike Drob commented on ZOOKEEPER-4519:
--------------------------------------

[~maoling] - any chance of a backport to 3.8.x or 3.7.x for this? I don't know how long the release cycle for 3.9 is going to end up taking and this seems pretty safe to apply to other branches as a change.

> Testable interface should have a testableCloseSocket() method
> -------------------------------------------------------------
>
>                 Key: ZOOKEEPER-4519
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4519
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: java client
>            Reporter: Houston Putman
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.9.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The {{ClientCnxn}} class has a protected function {{testableCloseSocket()}}, which allows applications to test how their system will respond if the Zookeeper socket connection is closed.
> This would be a very easy feature to add to the {{Testable}} interface, as the {{ZookeeperTestable}} class has access to a {{ClientCnxn}} that it could easily pass the {{testableCloseSocket()}} call to. That way applications wanting to test this do not need to rely on the {{tests}} artifacts in order to use this method, as they currently do.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)