[
https://issues.apache.org/jira/browse/CASSANDRA-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stu Hood updated CASSANDRA-1895:
--------------------------------
Priority: Major (was: Critical)
Summary: Loadbalance during gossip issues leaves cluster in bad state
(was: Loadbalance in trunk leaves cluster in bad state)
After a rebase and changes to the EC2 images I was using, I'm no longer able to
reproduce this against either 0.7 or trunk.
Nick noticed some gossip related problems in the attached logs, so I'm going to
chalk this up to _either_ a bad rebase, or problems related to bootstrapping
during gossip problems. Nick: could you chime in with details, and whether you
think those gossip issues might be worth pursuing?
> Loadbalance during gossip issues leaves cluster in bad state
> ------------------------------------------------------------
>
> Key: CASSANDRA-1895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1895
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Stu Hood
> Assignee: Stu Hood
> Fix For: 0.8
>
> Attachments: logs.tgz, ring-views.txt
>
>
> Running loadbalance against a node in a 4 node cluster leaves gossip in a
> wonky state.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
