[
https://issues.apache.org/jira/browse/CASSANDRA-10072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701429#comment-14701429
]
Jim Witschey commented on CASSANDRA-10072:
------------------------------------------
I have been running that branch of the Python driver. I'm not sure what fixed
it, but the test failures this caused on CassCI are fixed now. Just for the
record, the tests were:
{code}
largecolumn_test.py:TestLargeColumn.cleanup_test
bootstrap_test.py:TestBootstrap.decommissioned_wiped_node_can_join_test
bootstrap_test.py:TestBootstrap.killed_wiped_node_cannot_join_test
bootstrap_test.py:TestBootstrap.manual_bootstrap_test
bootstrap_test.py:TestBootstrap.read_from_bootstrapped_node_test
bootstrap_test.py:TestBootstrap.shutdown_wiped_node_cannot_join_test
consistency_test.py:TestAccuracy.test_network_topology_strategy_users
consistency_test.py:TestAccuracy.test_simple_strategy_users
consistency_test.py:TestAvailability.test_network_topology_strategy
consistency_test.py:TestAvailability.test_simple_strategy
replace_address_test.py:TestReplaceAddress.replace_first_boot_test
replace_address_test.py:TestReplaceAddress.replace_shutdown_node_test
replace_address_test.py:TestReplaceAddress.replace_stopped_node_test
replace_address_test.py:TestReplaceAddress.replace_with_reset_resume_state_test
replace_address_test.py:TestReplaceAddress.resumable_replace_test
{code}
And they stopped failing here:
http://cassci.datastax.com/view/trunk/job/trunk_dtest/485/testReport/junit/
I couldn't find any major changes to the {{cassandra-test}} branch of the
Python driver during the last few days, so I don't think that changes things.
So, who knows why it's fixed, but it seems to be. I'll close this.
> "Replica(s) failed to execute read" on simple select on stress-created table
> with >1 nodes
> ------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10072
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10072
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jim Witschey
> Assignee: Marcus Eriksson
> Fix For: 3.0 beta 2
>
> Attachments: repro.sh
>
>
> This looks similar to CASSANDRA-9825, though that was marked as resolved.
> To reproduce, create a multi-node cluster and insert values using stress.
> Then, try to run a {{SELECT}} statement on the {{keyspace1.standard1}} table
> created by stress.
> Running the select through the Python driver, I consistently get the result
> {code}
> cassandra.ReadFailure: code=1300 [Replica(s) failed to execute read]
> message="Operation failed - received 0 responses and 1 failures"
> info={'failures': 1, 'received_responses': 0, 'required_responses': 1,
> 'consistency': 'ONE'}
> {code}
> I've attached a script that reproduces it via the {{ccm}} CLI. As the script
> also demonstrates, the error doesn't show under 2.2, or when there is only 1
> node in the cluster.
> In the repro script, I've also included a commented-out insertion via cqlsh.
> If you uncomment that and comment out the stress line, the script
> demonstrates that the error doesn't occur when the table was created/inserted
> into via cqlsh.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
