[jira] [Updated] (CASSANDRA-14251) View replica is not written to pending endpoint when base replica is also view replica

["Paulo Motta (JIRA)" <ji...@apache.org>]

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

Paulo Motta updated CASSANDRA-14251:
------------------------------------
       Resolution: Fixed
         Reviewer: ZhaoYang
    Reproduced In: 3.11.1, 3.0.15  (was: 3.0.15, 3.11.1)
           Status: Resolved  (was: Patch Available)

Updated {{NEWS.TXT}} wording to state that potentially affected users must run repair in the base table and subsequently on the views, after [mailing list discussion|https://www.mail-archive.com/dev@cassandra.apache.org/msg12128.html].

Committed fix as {{c67338989f17257d3be95212ca6ecb4b83009326}} to cassandra-3.0 and merged up to cassandra-3.11 and trunk and dtest as {{8fa87f63dec7dd636473b620071d264893a19df8}}. Thanks for the review [~jasonstack].

> View replica is not written to pending endpoint when base replica is also view replica
> --------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14251
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14251
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Materialized Views
>            Reporter: Paulo Motta
>            Assignee: Paulo Motta
>            Priority: Major
>             Fix For: 4.0, 3.0.17, 3.11.3
>
>
> From the [dev list|https://www.mail-archive.com/dev@cassandra.apache.org/msg12084.html]:
> bq. There's an optimization that when we're lucky enough that the paired view replica is the same as this base replica, mutateMV doesn't use the normal view-mutation-sending code (wrapViewBatchResponseHandler) and just writes the mutation locally. In particular, in this case we do NOT write to the pending node (unless I'm missing something). But, sometimes all replicas will be paired with themselves - this can happen for example when number of nodes is equal to RF, or when the base and view table have the same partition keys (but different clustering keys). In this case, it seems the pending node will not be written at all...
> This was a regression from CASSANDRA-13069 and the original behavior should be restored.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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