[
https://issues.apache.org/jira/browse/CASSANDRA-10816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089482#comment-15089482
]
Vovodroid commented on CASSANDRA-10816:
---------------------------------------
Hi,
in branch *3.0.2 commit SHA a5c731b5* CHANGES.txt contains
{code}
Merged from 2.2:
* Fix regression on split size in CqlInputFormat (CASSANDRA-10835)
* Better handling of SSL connection errors inter-node (CASSANDRA-10816)
{code}
but I don't see changes from 3.0 patch in the branch nor in commit neither in
current code. Did I miss something?
> Explicitly handle SSL handshake errors during connect()
> -------------------------------------------------------
>
> Key: CASSANDRA-10816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10816
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Reporter: Stefan Podkowinski
> Assignee: Stefan Podkowinski
> Fix For: 2.2.5, 3.0.3, 3.2
>
>
> Diagnosing internode SSL issues can be a problem as any messaging
> {{IOException}} before this patch is just logged to debug, which is likely
> not enabled in most cases. Logs will just show nothing in case of any
> problems with SSL certs.
> Also the implemented retry semantics in {{OutboundTcpConnection}} will not
> make much sense for SSL handshake errors and will cause unnecessary load for
> both peers.
> The proposed patch will explicitly catch {{SSLHandshakeException}}, log them
> to error and abort connect().
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
