cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brandon Williams (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-4317) AssertionError in handleStateNormal in a mixed cluster
Date Tue, 19 Jun 2012 16:23:44 GMT


Brandon Williams updated CASSANDRA-4317:

    Attachment: 0002-Check-both-ms-and-gossip-for-version-when-handling-sta.txt

The first patch is CASSANDRA-4101 rebased, which gossips the net version.

The second adds a way to see is MS _really_ knows the version (so that we don't have to mess
with its current behavior) and encapsulates the logic to check both it and gossip to determine
if hostids should be used inside SS, replacing all the current checks there as well.
> AssertionError in handleStateNormal in a mixed cluster
> ------------------------------------------------------
>                 Key: CASSANDRA-4317
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2
>            Reporter: Brandon Williams
>            Assignee: Brandon Williams
>             Fix For: 1.2
>         Attachments: 0001-Gossip-current-network-version.txt, 0002-Check-both-ms-and-gossip-for-version-when-handling-sta.txt
> In a 3 node cluster with one seed on trunk, a member on trunk, and another member on
a previous version, the following occurs only on the non-seed trunk member:
> {noformat}
> ERROR 16:44:18,708 Exception in thread Thread[GossipStage:1,5,main]
> java.lang.AssertionError
>         at org.apache.cassandra.service.StorageService.handleStateNormal(
>         at org.apache.cassandra.service.StorageService.onChange(
>         at org.apache.cassandra.service.StorageService.onJoin(
>         at org.apache.cassandra.gms.Gossiper.handleMajorStateChange(
>         at org.apache.cassandra.gms.Gossiper.applyStateLocally(
>         at org.apache.cassandra.gms.GossipDigestAck2VerbHandler.doVerb(
>         at
>         at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> {noformat}
> This doesn't repro if a non-trunk member is the seed, however upgrading the seed first
should still be valid.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message