You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (Jira)" <ji...@apache.org> on 2022/02/15 23:13:00 UTC
[jira] [Comment Edited] (CASSANDRA-17387) Test failure: dtest-offheap.counter_test.TestCounters.test_13691
[ https://issues.apache.org/jira/browse/CASSANDRA-17387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17492898#comment-17492898 ]
Brandon Williams edited comment on CASSANDRA-17387 at 2/15/22, 11:12 PM:
-------------------------------------------------------------------------
This test [only runs|https://github.com/apache/cassandra-dtest/blob/trunk/counter_test.py#L20] with offheap objects on 3.11, since they are disabled in 3.0. The tested scenario involves old counter shards, so it first [installs 2.0.17|https://github.com/apache/cassandra-dtest/blob/trunk/counter_test.py#L33]. In the case of offheap memtables, this is too late for the [dtest setup|https://github.com/apache/cassandra-dtest/blob/trunk/dtest_setup.py#L428] which is applied without discretion, so it's actually 2.0 complaining here about a parameter from the (not so near) future. I don't see how this ever could have worked since the addition of offheap memtables to the dtests, and I don't think using them is particularly valuable for this test, so the simplest thing to do is skip this test when offheap is requested - [done here.|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17387]
was (Author: brandon.williams):
This test [only runs|https://github.com/apache/cassandra-dtest/blob/trunk/counter_test.py#L20] with offheap objects on 3.11, since they are disabled in 3.0. The tested scenario involves old counter shards, so it first [installs 2.0.17|https://github.com/apache/cassandra-dtest/blob/trunk/counter_test.py#L33]. In the case of offheap memtables, this is too late for the [dtest setup|https://github.com/apache/cassandra-dtest/blob/trunk/dtest_setup.py#L428] which is applied without discretion, so it's actually 2.0 complaining here about a parameter from the (not so near) future. I don't see how this ever could have worked since the addition of offheap to the dtests, and I don't think using them is particularly valuable for this test, so the simplest thing to do is skip this test when offheap is requested - [done here.|https://github.com/driftx/cassandra-dtest/tree/CASSANDRA-17387]
> Test failure: dtest-offheap.counter_test.TestCounters.test_13691
> ----------------------------------------------------------------
>
> Key: CASSANDRA-17387
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17387
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
> Reporter: Ekaterina Dimitrova
> Assignee: Brandon Williams
> Priority: Urgent
> Fix For: 3.11.x
>
>
> This test fails only off heap on 3.11, hard to say when it started as it was always failing since we have Butler. Marking it critical as it shows breaking config change.
> h3. Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors: [ERROR [main] 2022-02-10 05:06:27,462 DatabaseDescriptor.java (line 117) Fatal configuration error org.apache.cassandra.exceptions.ConfigurationException: Invalid yaml. Please remove properties [memtable_allocation_type] from your cassandra.yaml at org.apache.cassandra.config.YamlConfigurationLoader$MissingPropertiesChecker.check(YamlConfigurationLoader.java:137) at org.apache.cassandra.config.YamlConfigurationLoader.loadConfig(YamlConfigurationLoader.java:100) at
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org