You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Aleksey Yeschenko (JIRA)" <ji...@apache.org> on 2017/08/26 00:14:00 UTC

[jira] [Updated] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking

     [ https://issues.apache.org/jira/browse/CASSANDRA-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aleksey Yeschenko updated CASSANDRA-13809:
------------------------------------------
    Attachment:     (was: placeholder_patch.txt)

> 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
>
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org