[jira] [Comment Edited] (CASSANDRA-10674) Materialized View SSTable streaming/leaving status race on decommission

["T Jake Luciani (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-10674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14996551#comment-14996551 ] 

T Jake Luciani edited comment on CASSANDRA-10674 at 11/9/15 1:57 PM:
---------------------------------------------------------------------

[~yukim] are there any tickets to address the latter already opened?

Also, according to Joel this only happens when gossip doesn't fully propagate in 30 seconds.


was (Author: tjake):
@yukim are there any tickets to address the latter already opened?

Also, according to Joel this only happens when gossip doesn't fully propagate in 30 seconds.

> Materialized View SSTable streaming/leaving status race on decommission
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-10674
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10674
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Coordination, Distributed Metadata
>            Reporter: Joel Knighton
>             Fix For: 3.1
>
>         Attachments: leaving-node-debug.log, receiving-node-debug.log
>
>
> On decommission of a node in a cluster with materialized views, it is possible for the decommissioning node to begin streaming sstables for an MV base table before the receiving node is aware of the leaving status.
> The materialized view base/view replica pairing checks pending endpoints to handle the case when an sstable is received from a leaving node; without the leaving message, this check breaks and an exception is thrown. The streamed sstable is never applied.
> Logs from a decommissioning node and a node receiving such a stream are attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)