[
https://issues.apache.org/jira/browse/CASSANDRA-5498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636384#comment-13636384
]
Jonathan Ellis commented on CASSANDRA-5498:
-------------------------------------------
I'm not convinced that we should turn an internal bug into a UAE, although I'd
be fine with an assert to make more clear what we expect. (Pretty sure Thrift
will catch it and return an InternalError, so clients shouldn't be just left
hanging.)
Separately, I note that TokenMetadata.getWriteEndpoints is
ReplicationStrategy-agnostic. If you have any bootstrap action going on, that
could be causing your problem. (Similar bug in CASSANDRA-5424.)
> 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.1.12, 1.2.5, 2.0
>
> Attachments: 5498-v1.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
