You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Zhao Yang (Jira)" <ji...@apache.org> on 2020/10/02 15:21:00 UTC
[jira] [Created] (CASSANDRA-16174) During bootstrap streaming,
skipping write path may create orphan MV rows
Zhao Yang created CASSANDRA-16174:
-------------------------------------
Summary: During bootstrap streaming, skipping write path may create orphan MV rows
Key: CASSANDRA-16174
URL: https://issues.apache.org/jira/browse/CASSANDRA-16174
Project: Cassandra
Issue Type: Bug
Components: Feature/Materialized Views
Reporter: Zhao Yang
CASSANDRA-13065 improves the speed of bootstrap streaming by skipping write path for base table with MV.
Unfortunately during bootstrapping, the bootstrapping node may receive a base write that is already deleted or shadowed on other replicas, but the bootstrapping node didn't receive all sstables yet thus bootstapping node may create an orphan view row based on received sstables. Without write path, the newer version data will not create tombstone to shadow orphan view row.
For example, node-A has a base sstable containing: "k=1, v=1@2019", but bootstrapping node didn't receive it yet. A write "k=1, v=0@2018" hitting on bootstrapping node will create an orphan view row: "v=0@2018, k=1". Applying streaming sstables from bootstrap or rebuild through write path can help, but that's something we want to get rid of.
--
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