[
https://issues.apache.org/jira/browse/KAFKA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549829#comment-16549829
]
ASF GitHub Bot commented on KAFKA-3702:
---------------------------------------
rajinisivaram opened a new pull request #5397: KAFKA-3702: Change log level of
SSL close_notify failure
URL: https://github.com/apache/kafka/pull/5397
SslTransportLayer currently closes the SSL engine and logs a warning if
`close_notify` message canot be sent because the remote end closed its
connection. This tends to fill up broker logs, especially when using clients
which close connections immediately. Since this log entry is not very useful
anyway, it would be better to log at debug level.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> SslTransportLayer.close() does not shutdown gracefully
> ------------------------------------------------------
>
> Key: KAFKA-3702
> URL: https://issues.apache.org/jira/browse/KAFKA-3702
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.0.0
> Reporter: Rajini Sivaram
> Assignee: Rajini Sivaram
> Priority: Major
>
> The warning "Failed to send SSL Close message" occurs very frequently when
> SSL connections are closed. Close should write outbound data and shutdown
> gracefully.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
