[ 
https://issues.apache.org/jira/browse/CASSANDRA-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142492#comment-16142492
 ] 

Aleksey Yeschenko commented on CASSANDRA-13809:
-----------------------------------------------

Thanks. Committed as 
[c6dec2f0e02eb3ae9b9d070ec09cf822eda6bd2a|https://github.com/apache/cassandra/commit/c6dec2f0e02eb3ae9b9d070ec09cf822eda6bd2a]
 to 2.2. And the dtest too.

> Make BatchlogManagerMBean.forceBatchlogReplay() blocking
> --------------------------------------------------------
>
>                 Key: CASSANDRA-13809
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13809
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Coordination
>            Reporter: Aleksey Yeschenko
>            Assignee: Aleksey Yeschenko
>            Priority: Minor
>             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]

Reply via email to