[
https://issues.apache.org/jira/browse/CASSANDRA-13629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16059479#comment-16059479
]
Andrés de la Peña commented on CASSANDRA-13629:
-----------------------------------------------
Here is a very simple patch:
||[trunk|https://github.com/apache/cassandra/compare/trunk...adelapena:13629-trunk]|[utests|http://cassci.datastax.com/view/Dev/view/adelapena/job/adelapena-13629-trunk-testall/]|[dtests|http://cassci.datastax.com/view/Dev/view/adelapena/job/adelapena-13629-trunk-dtest/]|
It throws a blocking replay of the batchlog right before starting the native
transport service. I'm not sure about if this is the best place/moment to do
so.
Also, the possible exceptions in the initial batchlog replay are passed to the
JVM stability inspector, maybe we should simply stop the JVM in case of a
failure in the initial batchlog replay.
What do you think?
> 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: [email protected]
For additional commands, e-mail: [email protected]
