[ https://issues.apache.org/jira/browse/CASSANDRA-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153360#comment-16153360 ]
Aleksey Yeschenko commented on CASSANDRA-13809: ----------------------------------------------- The dtests aren't for it, it's the other way around. I have no idea how and why are they failing, however. Ran each of them dozens of times locally after I started seeing the failures on jenkins, and they never fail. > 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: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org