[
https://issues.apache.org/jira/browse/CASSANDRA-6590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13894980#comment-13894980
]
Brandon Williams commented on CASSANDRA-6590:
---------------------------------------------
bq. the if (!localState.isAlive()) check is problematic, because while it got
rid of the repeated UP messages, it also seemed to introduce a race situation
Nevermind that part, it was something else.
I'm still seeing repeated messages when healing the partition though:
{noformat}
INFO 20:16:56,176 Handshaking version with /10.208.8.63
INFO 20:16:56,186 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,187 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,187 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,190 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,190 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,190 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,191 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,191 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,191 InetAddress /10.208.8.63 is now UP
INFO 20:16:56,193 InetAddress /10.208.8.63 is now UP
{noformat}
What I mentioned before about the block in handleMajorStateChange and the yaml
option still applies.
> Gossip does not heal after a temporary partition at startup
> -----------------------------------------------------------
>
> Key: CASSANDRA-6590
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6590
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Brandon Williams
> Assignee: Vijay
> Fix For: 2.0.6
>
> Attachments: 0001-CASSANDRA-6590.patch, 0001-logging-for-6590.patch,
> 6590_disable_echo.txt
>
>
> See CASSANDRA-6571 for background. If a node is partitioned on startup when
> the echo command is sent, but then the partition heals, the halves of the
> partition will never mark each other up despite being able to communicate.
> This stems from CASSANDRA-3533.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
