[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking
[
https://issues.apache.org/jira/browse/CASSANDRA-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16153365#comment-16153365
]
Marcus Eriksson commented on CASSANDRA-13809:
-
created CASSANDRA-13842
> 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
[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking
[
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
[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking
[
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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking
[
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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking
[
https://issues.apache.org/jira/browse/CASSANDRA-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142489#comment-16142489
]
Jeff Jirsa commented on CASSANDRA-13809:
+1
> 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.x
>
>
> 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
[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking
[
https://issues.apache.org/jira/browse/CASSANDRA-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142483#comment-16142483
]
Aleksey Yeschenko commented on CASSANDRA-13809:
---
Dtests in question [here|https://github.com/apache/cassandra-dtest/pull/7].
> 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.x
>
>
> 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
[jira] [Commented] (CASSANDRA-13809) Make BatchlogManagerMBean.forceBatchlogReplay() blocking
[
https://issues.apache.org/jira/browse/CASSANDRA-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16142482#comment-16142482
]
Patrick McFadin commented on CASSANDRA-13809:
-
Placeholder reply to [~iamaleksey]
> 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.x
>
>
> 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
