[ZOOKEEPER-1547] Test robustness of client using SASL in the presence of dropped requests

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Eugene Joseph Koontz
• Created: 04/Sep/12 20:42
• Updated: 06/Nov/12 05:13

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

Issue Links

• relates to: ZOOKEEPER-1437 Client uses session before SASL authentication complete