[
https://issues.apache.org/jira/browse/KAFKA-2672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965556#comment-14965556
]
Jason Gustafson commented on KAFKA-2672:
----------------------------------------
[~ijuma] The point of clearing the requests after poll was to keep the
ConsumerNetworkClient implementation simple and easy to understand. After a
call to poll, all requests will either be successfully transmitted on the wire,
or will fail. We could alternatively have the ConsumerNetworkClient hold onto
requests that couldn't be sent and try again later (I assumed we will do
eventually at some point), but that will make the implementation trickier. In
this case, the exception should be harmless since the fetch should be requested
again on the next call to KafkaConsumer.poll().
> 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: Neha Narkhede
> Fix For: 0.9.0.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)
