[
https://issues.apache.org/jira/browse/CASSANDRA-13629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16069680#comment-16069680
]
Andrés de la Peña edited comment on CASSANDRA-13629 at 6/30/17 8:15 AM:
------------------------------------------------------------------------
It seems that since
[CASSANDRA-13065|https://issues.apache.org/jira/browse/CASSANDRA-13065] the
data received during bootstrap is not sent to batchlog. Since the batchlog is
empty when bootstrap finishes, this ticket is not necessary.
was (Author: adelapena):
It sees that since
[CASSANDRA-13065|https://issues.apache.org/jira/browse/CASSANDRA-13065] the
data received during bootstrap is not sent to batchlog. Since the batchlog is
empty when bootstrap finishes, this ticket is not necessary.
> 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
>
> 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
