You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Lebresne (JIRA)" <ji...@apache.org> on 2013/02/25 17:02:15 UTC

[jira] [Updated] (CASSANDRA-5284) Possible assertion triggered in SliceFromReadCommand

     [ https://issues.apache.org/jira/browse/CASSANDRA-5284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sylvain Lebresne updated CASSANDRA-5284:
----------------------------------------

    Attachment: 5284.txt
    
> Possible assertion triggered in SliceFromReadCommand
> ----------------------------------------------------
>
>                 Key: CASSANDRA-5284
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5284
>             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: http://www.atlassian.com/software/jira