[
https://issues.apache.org/jira/browse/CASSANDRA-13629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075719#comment-16075719
]
Paulo Motta commented on CASSANDRA-13629:
-----------------------------------------
bq. CASSANDRA-13065, which was considered an improvement, solves this problem
only for 4.0. If now we see it as a bug fix we might want to port it back to
other branches. Paulo Motta, what do you think?
Actually CASSANDRA-13065 is an improvement which happens to fix this on 4.0,
but it's a change in the MV design and should be kept to 4.0 only. If solving
this on 3.0, the less disruptive way would be to use the approach discussed
before of waiting for batchlog replay after bootstrap.
> Wait for batchlog replay during bootstrap
> -----------------------------------------
>
> Key: CASSANDRA-13629
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13629
> Project: Cassandra
> Issue Type: Sub-task
> Components: Materialized Views
> Reporter: Andrés de la Peña
> Assignee: Andrés de la Peña
> Fix For: 4.0
>
>
> As part of the problem described in
> [CASSANDRA-13162|https://issues.apache.org/jira/browse/CASSANDRA-13162], the
> bootstrap logic won't wait for the backlogged batchlog to be fully replayed
> before changing the new bootstrapping node to "UN" state. We should wait for
> batchlog replay before making the node available.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
