[
https://issues.apache.org/jira/browse/CASSANDRA-10686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15068050#comment-15068050
]
Paulo Motta commented on CASSANDRA-10686:
-----------------------------------------
The problem of fixing on dtest only is that clients will potentially miss
schema mismatches after DDL if they set {{client_timeout >
max_schema_agreement_wait}}, so this fix would guarantee {{client_timeout <
max_schema_agreement_wait}} while
[PYTHON-458|https://datastax-oss.atlassian.net/browse/PYTHON-458] is not ready.
> cqlsh schema refresh on timeout dtest is flaky
> -----------------------------------------------
>
> Key: CASSANDRA-10686
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10686
> Project: Cassandra
> Issue Type: Bug
> Components: Testing, Tools
> Reporter: Joel Knighton
> Assignee: Paulo Motta
> Priority: Minor
>
> [flaky 3.0
> runs|http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/lastCompletedBuild/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_refresh_schema_on_timeout_error/history/]
> [flaky 2.2
> runs|http://cassci.datastax.com/job/cassandra-2.2_dtest/381/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_refresh_schema_on_timeout_error/history/]
> [flaky 2.1
> runs|http://cassci.datastax.com/job/cassandra-2.1_dtest/324/testReport/cqlsh_tests.cqlsh_tests/TestCqlsh/test_refresh_schema_on_timeout_error/history/]
> As far as I can tell, the issue could be with the test or the original issue.
> Pinging [~pauloricardomg] since he knows this best.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
