-
Type:
Task
-
Status: Open
-
Priority:
Normal
-
Resolution: Unresolved
-
Fix Version/s: 4.x
-
Component/s: Feature/Materialized Views
-
Labels:None
-
Epic Link:
-
Change Category:Quality Assurance
-
Complexity:Normal
-
Platform:All
-
Impacts:None
The main purpose of this ticket to get a better understanding about 4.0 MV status as a guideline for future improvements. I don't think it should block 4.0 release since it's already marked as experimental.
Main areas to test:
- Write perf: We expect to see 10% write throughput drop per MV added.
- Attached C40_MV.png is alpha-4, 5-node, rf3 MV write tests: with 1 mv, throughput dropped 50%
- Read perf: identical to normal table
- Bootstrap/Decommision: no write-path required since
CASSANDRA-13065 - Repair: write path required
- Chaos monkey: take down coordinator/base-replica/view-replica during read/write/token-movement and verify data consistency (may need a tool)
- Hint Replay: able to throttle if table has MV - CASSANDRA-13810
- Schema race: create/drop - CASSANDRA-15845/CASSANDRA-15918
- is a parent of
-
CASSANDRA-13810 Overload because of hint pressure + MVs
-
- Open
-
-
CASSANDRA-12734 Materialized View schema file for snapshots created as tables
-
- Open
-
-
CASSANDRA-12888 Incremental repairs broken for MVs and CDC
-
- Open
-
-
CASSANDRA-14168 Throw error when attempting to mutate non-existant table
-
- Open
-
-
CASSANDRA-12783 Break up large MV mutations to prevent OOMs
-
- In Progress
-
-
CASSANDRA-16172 materialized view can return stale data even with R+W>N
-
- Triage Needed
-
-
CASSANDRA-16174 During bootstrap streaming, skipping write path may create orphan MV rows
-
- Triage Needed
-
-
CASSANDRA-16175 Avoid removing batch when it's not created during view replication
-
- Triage Needed
-
- is related to
-
CASSANDRA-16076 Batch schema statements to create multiple SASI and MV at once to reduce disk IO
-
- Open
-
-
CASSANDRA-13826 Specialize row structure to support complex Materialized Views liveness
-
- Open
-