[
https://issues.apache.org/jira/browse/KAFKA-2581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908902#comment-14908902
]
Ismael Juma commented on KAFKA-2581:
------------------------------------
Yes, SSL can certainly introduce new failure scenarios due to more complicated
buffer management, see
https://github.com/apache/kafka/commit/54dd6e3ad7038ce4a32108b44153ec81caff2c68
for example. It's not a matter of it works or it doesn't work, unfortunately.
The additional latency while establishing connections due to the handshake can
also trigger some weird problems (`ConsumerPerformance` times out before it
does any work as another example, Ben fixed this in one of his branches).
So, to answer your question, I would want to have a test that was simpler (we
already have that), but I would also want to have one that shows that things
work in more complex scenarios (we don't have that).
To be clear, I am not saying that _every_ test is useful. I am not opposed to
selecting the tests in some way. But from this conversation, it is clear that I
think a lot more tests would be useful than you do at this point. :)
> Run all existing ducktape tests with SSL-enabled clients and brokers
> --------------------------------------------------------------------
>
> Key: KAFKA-2581
> URL: https://issues.apache.org/jira/browse/KAFKA-2581
> Project: Kafka
> Issue Type: Sub-task
> Components: security
> Affects Versions: 0.9.0.0
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Fix For: 0.9.0.0
>
>
> New ducktape tests for testing SSL are being added under KAFKA-2417. This
> task will enable existing ducktape tests to be run with SSL-enabled brokers
> and clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
