[ https://issues.apache.org/jira/browse/CASSANDRA-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664199#comment-13664199 ]
Jonathan Ellis edited comment on CASSANDRA-5498 at 5/22/13 3:46 PM: -------------------------------------------------------------------- But I don't see how 0.7 would return an exception at all; it would just close the connection uncleanly. was (Author: jbellis): But I don't see how 0.7 would return an exception; it would just close the connection uncleanly. > Possible NPE on EACH_QUORUM writes > ---------------------------------- > > Key: CASSANDRA-5498 > URL: https://issues.apache.org/jira/browse/CASSANDRA-5498 > Project: Cassandra > Issue Type: Bug > Components: Core > Affects Versions: 1.1.10 > Reporter: Jason Brown > Assignee: Jason Brown > Priority: Minor > Labels: each_quorum, ec2 > Fix For: 1.2.6 > > Attachments: 5498-v1.patch, 5498-v2.patch > > > When upgrading from 1.0 to 1.1, we observed that > DatacenterSyncWriteResponseHandler.assureSufficientLiveNodes() can throw an > NPE if one of the writeEndpoints has a DC that is not listed in the keyspace > while one of the nodes is down. We observed this while running in EC2, and > using the Ec2Snitch. The exception typically was was brief, but a certain > segment of writes (using EACH_QUORUM) failed during that time. > This ticket will address the NPE in DSWRH, while a followup ticket will be > created once we get to the bottom of the incorrect DC being reported from > Ec2Snitch. -- 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