You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mark Guzman (JIRA)" <ji...@apache.org> on 2011/02/28 01:56:36 UTC
[jira] Updated: (CASSANDRA-2254) assert when using CL.EACH_QUORUM
[ https://issues.apache.org/jira/browse/CASSANDRA-2254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mark Guzman updated CASSANDRA-2254:
-----------------------------------
Attachment: 0001-Fixing-CASSANDRA-2254-DatacenterSyncWriteResponseHea.patch
Patch that changes the assert to match what I believe is the intent of the check, basically s/LOCAL_QUORUM/EACH_QUORUM/.
> assert when using CL.EACH_QUORUM
> --------------------------------
>
> Key: CASSANDRA-2254
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2254
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7.2
> Environment: RH Linux
> Reporter: Mark Guzman
> Attachments: 0001-Fixing-CASSANDRA-2254-DatacenterSyncWriteResponseHea.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When using the NetworkTopology strategy, I am able to write using CL.LOCAL_QUORUM. When I attempt to write using CL.EACH_QUORUM, an assert is hit in DatacenterSyncWriteResponseHandler. Tracing the call through to the NetworkTopology code, it seems that this particular handler is only used when CL = EACH_QUORUM, yet the code asserts.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira