You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Berenguer Blasi (Jira)" <ji...@apache.org> on 2020/06/04 12:35:00 UTC
[jira] [Commented] (CASSANDRA-14571) Fix race condition in MV
build/propagate when there is existing data in the base table
[ https://issues.apache.org/jira/browse/CASSANDRA-14571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125887#comment-17125887 ]
Berenguer Blasi commented on CASSANDRA-14571:
---------------------------------------------
Looking at 4.0 test failures this one was failing again. There is still a window for schema agreement to happen but the view not be available yet in some nodes. Marking the flaky test in CASSANDRA-15855 and CASSANDRA-15845 to address that root cause eventually. #justfyi
> Fix race condition in MV build/propagate when there is existing data in the base table
> --------------------------------------------------------------------------------------
>
> Key: CASSANDRA-14571
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14571
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Normal
> Fix For: 4.0, 4.0-alpha1
>
>
> CASSANDRA-13426 exposed a race in MV initialisation and building, which now breaks, consistently, {{materialized_views_test.py::TestMaterializedViews::test_populate_mv_after_insert_wide_rows}}.
> CASSANDRA-14168 is also directly related.
--
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