cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5498) Possible NPE on EACH_QUORUM writes
Date Mon, 03 Jun 2013 17:39:20 GMT


Jeremiah Jordan commented on CASSANDRA-5498:

I don't think an exception is being caught and passed to the client.  I think the connection
closes so org.apache.thrift.TApplicationException gets thrown.

[~jasobrown] have you done any more debug on what is causing this?
> Possible NPE on EACH_QUORUM writes
> ----------------------------------
>                 Key: CASSANDRA-5498
>                 URL:
>             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:

View raw message