[ 
https://issues.apache.org/jira/browse/CASSANDRA-15921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ZhaoYang updated CASSANDRA-15921:
---------------------------------
    Description: 
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|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x].
** Attached C40_MV.png  is alpha-4, 5-node, rf3 MV write tests.
 * 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

  was:
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|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x].
 * 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


> 4.0 quality testing: Materialized View
> --------------------------------------
>
>                 Key: CASSANDRA-15921
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15921
>             Project: Cassandra
>          Issue Type: Task
>          Components: Feature/Materialized Views
>            Reporter: ZhaoYang
>            Assignee: ZhaoYang
>            Priority: Normal
>             Fix For: 4.x
>
>         Attachments: C40_MV.png
>
>
> 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|https://www.datastax.com/blog/2016/05/materialized-view-performance-cassandra-3x].
> ** Attached C40_MV.png  is alpha-4, 5-node, rf3 MV write tests.
>  * 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



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to