cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Miklosovic (Jira)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12774) Expose dc in Unavailable exception errors
Date Tue, 03 Aug 2021 07:42:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-12774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392065#comment-17392065
] 

Stefan Miklosovic commented on CASSANDRA-12774:
-----------------------------------------------

[~andrew.tolbert] what version of Cassandra have you seen this problem in?

> Expose dc in Unavailable exception errors
> -----------------------------------------
>
>                 Key: CASSANDRA-12774
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12774
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Legacy/CQL, Legacy/Observability
>            Reporter: Andy Tolbert
>            Priority: Low
>
> For protocol v5 or later, it could be useful if Unavailable optionally included the DC
that could not meet the CL.  
> For example. if a user has a keyspace with RF of { dc1: 3, dc2: 3 } and they make a query
at {{EACH_QUORUM}} and not enough replicas are available in dc2, an {{UnavailableException}}
will be sent to the client with X available and 2 required, but we don't know which DC failed.
 It looks like {{UnavailableException}} already has a constructor that takes in the DC (see
[here|https://github.com/apache/cassandra/blob/cassandra-3.0/src/java/org/apache/cassandra/exceptions/UnavailableException.java#L33])
so this could be feasible.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message