[
https://issues.apache.org/jira/browse/CASSANDRA-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153235#comment-16153235
]
Marcus Eriksson commented on CASSANDRA-13809:
---------------------------------------------
looks like the new dtests for this are broken?
http://cassci.datastax.com/view/cassandra-3.11/job/cassandra-3.11_dtest/160/testReport/
http://cassci.datastax.com/view/cassandra-3.0/job/cassandra-3.0_dtest/984/testReport/
> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> --------------------------------------------------------
>
> Key: CASSANDRA-13809
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
> Project: Cassandra
> Issue Type: Improvement
> Components: Coordination
> Reporter: Aleksey Yeschenko
> Assignee: Aleksey Yeschenko
> Priority: Trivial
> Fix For: 2.2.11
>
>
> In 3.0, {{BatchlogManagerMBean.forceBatchlogReplay()}} blocks until
> completion. In 2.2 it just submits a runnable and instaexits, which makes it
> impossible to create non-flaky dtests that rely on batchlog replay.
> [here|https://github.com/iamaleksey/cassandra/commits/13809-2.2] is a small
> 2.2-only commit that make the behaviour consistent between 2.2 and 3.0.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
