[
https://issues.apache.org/jira/browse/KAFKA-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-2672:
---------------------------
Fix Version/s: (was: 0.9.0.0)
0.9.1.0
Description:
When running new consumer with SSL, debug logs show these exceptions every time:
{quote}
[2015-10-19 20:57:43,389] DEBUG Fetch failed
(org.apache.kafka.clients.consumer.internals.Fetcher)
org.apache.kafka.clients.consumer.internals.SendFailedException
{quote}
The exception occurs because send is queued before SSL handshake is complete.
I am not sure if the exception is harmless, but it will be good to avoid the
exception either way since it feels like an exception that exists to handle
edge cases like buffer overflow rather than something in a normal code path.
was:
When running new consumer with SSL, debug logs show these exceptions every time:
{quote}
[2015-10-19 20:57:43,389] DEBUG Fetch failed
(org.apache.kafka.clients.consumer.internals.Fetcher)
org.apache.kafka.clients.consumer.internals.SendFailedException
{quote}
The exception occurs because send is queued before SSL handshake is complete.
I am not sure if the exception is harmless, but it will be good to avoid the
exception either way since it feels like an exception that exists to handle
edge cases like buffer overflow rather than something in a normal code path.
> SendFailedException when new consumer is run with SSL
> -----------------------------------------------------
>
> Key: KAFKA-2672
> URL: https://issues.apache.org/jira/browse/KAFKA-2672
> Project: Kafka
> Issue Type: Bug
> Components: consumer
> Reporter: Rajini Sivaram
> Assignee: Jason Gustafson
> Fix For: 0.9.1.0
>
>
> When running new consumer with SSL, debug logs show these exceptions every
> time:
> {quote}
> [2015-10-19 20:57:43,389] DEBUG Fetch failed
> (org.apache.kafka.clients.consumer.internals.Fetcher)
> org.apache.kafka.clients.consumer.internals.SendFailedException
> {quote}
> The exception occurs because send is queued before SSL handshake is
> complete. I am not sure if the exception is harmless, but it will be good to
> avoid the exception either way since it feels like an exception that exists
> to handle edge cases like buffer overflow rather than something in a normal
> code path.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
