[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633435#comment-14633435
]
T Jake Luciani commented on CASSANDRA-6477:
-------------------------------------------
bq. so, if we lose any two nodes, one of those nodes will be a base replica,
and the other will be an MV replica that is paired with one of the other base
replicas for one of the token ranges in the cluster
Keep in mind. If you loose any 2 nodes with vnodes you can't achieve quorum
anyway. In anycase this leads back to the whole availibility story I mentioned
earlier (why doing sync writes won't work) So we have batchlogs that I do
believe get us back to consistency once they replay.
> Materialized Views (was: Global Indexes)
> ----------------------------------------
>
> Key: CASSANDRA-6477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6477
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Carl Yeksigian
> Labels: cql
> Fix For: 3.0 beta 1
>
> Attachments: test-view-data.sh, users.yaml
>
>
> Local indexes are suitable for low-cardinality data, where spreading the
> index across the cluster is a Good Thing. However, for high-cardinality
> data, local indexes require querying most nodes in the cluster even if only a
> handful of rows is returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
