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

Andres de la Peña commented on CASSANDRA-16180:
-----------------------------------------------

[~maedhroz] I'm adding [a 
document|https://docs.google.com/document/d/1BBeGKla9tIPflZ2awkyfl5Hc_FTs3QYw98LWUnb1fTQ/edit?usp=sharing]
 describing the existing dtests for coordination. I think that they are in 
quite better shape than the ones we found for read repair during 
CASSANDRA-15977, which is unsurprising given how fundamental coordination is. 

After giving it a thought I think that splitting {{StorageProxy}} and trying to 
add some unit tests to the separated components is a good thing to do here, 
particularly for the range read logic, as you said. 

I also agree that it's better to leave Paxos/CAS out of the scope of this 
ticket.

> 4.0 quality testing: Coordination
> ---------------------------------
>
>                 Key: CASSANDRA-16180
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16180
>             Project: Cassandra
>          Issue Type: Task
>          Components: Test/unit
>            Reporter: Andres de la Peña
>            Assignee: Andres de la Peña
>            Priority: Normal
>             Fix For: 4.0
>
>
> This is a subtask of CASSANDRA-15579 focusing on coordination.
> I think that the main reference dtest for this is 
> [consistency_test.py|https://github.com/apache/cassandra-dtest/blob/master/consistency_test.py].
>  We should identify which other tests cover this and identify what should be 
> extended, similarly to what has been done with CASSANDRA-15977.
> [This 
> document|https://docs.google.com/document/d/1BBeGKla9tIPflZ2awkyfl5Hc_FTs3QYw98LWUnb1fTQ/edit?usp=sharing]
>  aims to list and describe the existing functional tests for coordination, so 
> we can have a broad view of what is currently covered. 



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to