[
https://issues.apache.org/jira/browse/ZOOKEEPER-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koontz updated ZOOKEEPER-1547:
-------------------------------------
Description:
ZK clients send SASL packets to ZK servers as request packets. However, what if
the server does not responds to the client's SASL packets with responses? In
this scenario, the server does not actually close the connection to the client,
it simply fails to respond to SASL requests. Make sure the client can cope with
this behavior.
Background:
In ZOOKEEPER-1437, Ben writes:
"[I]t would be great to add a test that simply drops responses to clients
without closing connections."
https://issues.apache.org/jira/browse/ZOOKEEPER-1437?focusedCommentId=13447477&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13447477
Also in ZOOKEEPER-1437 Rakesh writes: "I could see
DisconnectableZooKeeper.disconnect() has network delays/partition simulation
logic."
https://issues.apache.org/jira/browse/ZOOKEEPER-1437?focusedCommentId=13445704&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13445704
was:
ZK clients send SASL packets to ZK servers as request packets. However, what if
the server does not responds to the client's SASL packets with responses? The
server does not actually close the connection to the client, it simply fails to
respond to SASL requests. Make sure the client can cope with this behavior.
Background:
In ZOOKEEPER-1437, Ben writes:
"[I]t would be great to add a test that simply drops responses to clients
without closing connections."
https://issues.apache.org/jira/browse/ZOOKEEPER-1437?focusedCommentId=13447477&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13447477
Also in ZOOKEEPER-1437 Rakesh writes: "I could see
DisconnectableZooKeeper.disconnect() has network delays/partition simulation
logic."
https://issues.apache.org/jira/browse/ZOOKEEPER-1437?focusedCommentId=13445704&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13445704
> Test robustness of client using SASL in the presence of dropped requests
> ------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1547
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1547
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Eugene Koontz
>
> ZK clients send SASL packets to ZK servers as request packets. However, what
> if the server does not responds to the client's SASL packets with responses?
> In this scenario, the server does not actually close the connection to the
> client, it simply fails to respond to SASL requests. Make sure the client can
> cope with this behavior.
> Background:
> In ZOOKEEPER-1437, Ben writes:
> "[I]t would be great to add a test that simply drops responses to clients
> without closing connections."
> https://issues.apache.org/jira/browse/ZOOKEEPER-1437?focusedCommentId=13447477&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13447477
> Also in ZOOKEEPER-1437 Rakesh writes: "I could see
> DisconnectableZooKeeper.disconnect() has network delays/partition simulation
> logic."
> https://issues.apache.org/jira/browse/ZOOKEEPER-1437?focusedCommentId=13445704&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13445704
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
