cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-5284) Possible assertion triggered in SliceFromReadCommand
Date Mon, 25 Feb 2013 16:02:15 GMT


Sylvain Lebresne updated CASSANDRA-5284:

    Attachment: 5284.txt
> Possible assertion triggered in SliceFromReadCommand
> ----------------------------------------------------
>                 Key: CASSANDRA-5284
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.1.11
>         Attachments: 5284.txt
> In SliceFromReadCommand.maybeGenerateRetryCommand, the following assertion
> {noformat}
> assert maxLiveColumns <= count;
> {noformat}
> may actually fail. Namely, it asserts that no node has returned more columns that what
was asked for, which in general is true, but can not be if an expiring column is counted as
dead by the replica (but still send as a tombstone) but, due to clock difference, is actually
counted live by the coordinator.
> I note that this is similar to CASSANDRA-5149 in that fixing CASSANDRA-5149 would fix
this too, but in the meantime, this edge case is harmless so there is probably not much point
in keeping the assertion.

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

View raw message