[jira] [Commented] (CASSANDRA-11034) consistent_reads_after_move_test is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-11034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15124125#comment-15124125
]
Carl Yeksigian commented on CASSANDRA-11034:
+1
> consistent_reads_after_move_test is failing on trunk
>
>
> Key: CASSANDRA-11034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11034
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Marcus Eriksson
>Priority: Blocker
> Labels: dtest
> Fix For: 3.3
>
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> The novnode dtest
> {{consistent_bootstrap_test.TestBootstrapConsistency.consistent_reads_after_move_test}}
> is failing on trunk. See an example failure
> [here|http://cassci.datastax.com/job/trunk_novnode_dtest/274/testReport/consistent_bootstrap_test/TestBootstrapConsistency/consistent_reads_after_move_test/].
> On trunk I am getting an OOM of one of my C* nodes [node3], which is what
> causes the nodetool move to fail. Logs are attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11034) consistent_reads_after_move_test is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-11034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121906#comment-15121906
]
Marcus Eriksson commented on CASSANDRA-11034:
-
This is actually caused by CASSANDRA-10887 we don't see the same pending ranges
during the move as we did before, trying to figure out why
> consistent_reads_after_move_test is failing on trunk
>
>
> Key: CASSANDRA-11034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11034
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Marcus Eriksson
> Labels: dtest
> Fix For: 3.x
>
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> The novnode dtest
> {{consistent_bootstrap_test.TestBootstrapConsistency.consistent_reads_after_move_test}}
> is failing on trunk. See an example failure
> [here|http://cassci.datastax.com/job/trunk_novnode_dtest/274/testReport/consistent_bootstrap_test/TestBootstrapConsistency/consistent_reads_after_move_test/].
> On trunk I am getting an OOM of one of my C* nodes [node3], which is what
> causes the nodetool move to fail. Logs are attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (CASSANDRA-11034) consistent_reads_after_move_test is failing on trunk
[
https://issues.apache.org/jira/browse/CASSANDRA-11034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15115020#comment-15115020
]
Sylvain Lebresne commented on CASSANDRA-11034:
--
Assigning to [~krummas] because from the CI history, this look like it is
likely a regression from CASSANDRA-6696. That is, it starts failing
[there|http://cassci.datastax.com/job/trunk_novnode_dtest/259/changes], which
has a few other minor changes, but the server side OOM happens in {{Splitter}}
which was, I believe, introduced by this patch (see trace
[here|http://cassci.datastax.com/job/trunk_novnode_dtest/259/testReport/consistent_bootstrap_test/TestBootstrapConsistency/consistent_reads_after_move_test_2/]).
> consistent_reads_after_move_test is failing on trunk
>
>
> Key: CASSANDRA-11034
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11034
> Project: Cassandra
> Issue Type: Bug
>Reporter: Philip Thompson
>Assignee: Marcus Eriksson
> Labels: dtest
> Fix For: 3.x
>
> Attachments: node1.log, node1_debug.log, node2.log, node2_debug.log,
> node3.log, node3_debug.log
>
>
> The novnode dtest
> {{consistent_bootstrap_test.TestBootstrapConsistency.consistent_reads_after_move_test}}
> is failing on trunk. See an example failure
> [here|http://cassci.datastax.com/job/trunk_novnode_dtest/274/testReport/consistent_bootstrap_test/TestBootstrapConsistency/consistent_reads_after_move_test/].
> On trunk I am getting an OOM of one of my C* nodes [node3], which is what
> causes the nodetool move to fail. Logs are attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
