[
https://issues.apache.org/jira/browse/CASSANDRA-13018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872302#comment-15872302
]
Jeff Jirsa commented on CASSANDRA-13018:
----------------------------------------
In reading through this and talking to Jason, it does appear that the log line
is in the wrong place.
The only way we end up in this block is if the connect fails (or rather, if
we're unable to read the other side's version), but what we really want to
guard against in CASSANDRA-8768 is connecting to an incompatible version -
which is a few blocks down.
> Exceptions encountered calling getSeeds() breaks messaging service
> ------------------------------------------------------------------
>
> Key: CASSANDRA-13018
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13018
> Project: Cassandra
> Issue Type: Bug
> Components: Streaming and Messaging
> Reporter: Jeff Jirsa
> Assignee: Jeff Jirsa
> Labels: lhf
> Attachments:
> 0001-Better-handle-config-errors-during-outbound-connecti.patch
>
>
> OutboundTcpConnection.connect() calls getSeeds(). If getSeeds() throws an
> exception (for example, DD/Config invalid yaml error), messaging thread(s)
> break(s).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
