[
https://issues.apache.org/jira/browse/CASSANDRA-8592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353161#comment-14353161
]
Tyler Hobbs commented on CASSANDRA-8592:
----------------------------------------
The commitlog permissions were a good idea, but I think the sanest option may
be to add a special JVM flag to trigger write exceptions on the replica (e.g.
{{-Dcassandra.test.fail_writes}}). I'm open to other suggestions if anybody
else has ideas.
bq. Also, do we need to test with a V4 client? The dtest is still getting a
WriteTimeout because of the conversion to legacy exceptions which happens if
the protocol version is less than or equal to 3.
Yes, you'll want to open connections with the v4 protocol. The dtest
connection methods ({{patient_cql_connection()}}, etc) take a protocol_version
argument. You'll also need to change
{{o.a.c.transport.Server.CURRENT_VERSION}} to {{VERSION_4}} to allow Cassandra
to accept v4 connections.
bq. Are you happy to be the reviewer or shall I find someone else?
Sure, I can review this one.
> Add WriteFailureException
> -------------------------
>
> Key: CASSANDRA-8592
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8592
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Tyler Hobbs
> Assignee: Stefania
> Labels: client-impacting
> Fix For: 3.0
>
>
> Similar to what CASSANDRA-7886 did for reads, we should add a
> WriteFailureException and have replicas signal a failure while handling a
> write to the coordinator.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
