[jira] [Updated] (CASSANDRA-16695) cqlsh should prefer newer TLS version by default
[
https://issues.apache.org/jira/browse/CASSANDRA-16695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16695:
---
Fix Version/s: (was: 4.0-rc2)
4.0-rc
2.2.x
> cqlsh should prefer newer TLS version by default
>
>
> Key: CASSANDRA-16695
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16695
> Project: Cassandra
> Issue Type: Bug
> Components: Tool/cqlsh
>Reporter: Justin Chu
>Priority: Normal
> Labels: cqlsh
> Fix For: 4.0, 2.2.x, 3.0.x, 3.11.x, 4.0-rc, 4.x
>
>
> Some new JDK releases started to disable TLSv1.0 and TLSv1.1.
> [https://www.oracle.com/java/technologies/javase/8u291-relnotes.html]
>
> However, the code in:
> [https://github.com/apache/cassandra/blob/trunk/pylib/cqlshlib/sslhandling.py#L56-L65]
> is defaulting to those rather old versions,
> which could lead to the following problem:
> {code:java}
> ('Unable to connect to any servers', {'10.101.34.89:9042': error(1, u"Tried
> connecting to [('10.101.34.89', 9042)]. Last error: [SSL:
> WRONG_VERSION_NUMBER] wrong version number (_ssl.c:618)")}) {code}
>
> Python2 default TLS protocol
> [https://docs.python.org/2/library/ssl.html#ssl.PROTOCOL_TLS]
> Python3 default TLS protocol
> [https://docs.python.org/3/library/ssl.html#ssl.PROTOCOL_TLS]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16672) Retag ccm
[
https://issues.apache.org/jira/browse/CASSANDRA-16672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352283#comment-17352283
]
Berenguer Blasi commented on CASSANDRA-16672:
-
I was about to commit that CCM change from CASSANDRA-16644 but there are some
build problems today so I'll hold off to next week #justfyi
> Retag ccm
> -
>
> Key: CASSANDRA-16672
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16672
> Project: Cassandra
> Issue Type: Task
> Components: Test/dtest/python
>Reporter: Berenguer Blasi
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 3.0.25, 3.11.11, 4.0-rc2, 4.0, 4.1
>
>
> CCM repro's trunk is several commits ahead from {{cassandra-test}} tag.
> Probably an oversight but retagging needs CI to be ran just to make sure
> nothing broke in between.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16670) Flaky ViewComplexTest and InsertUpdateIfConditionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352281#comment-17352281 ] Berenguer Blasi commented on CASSANDRA-16670: - CI is green already, please find links in the PR. Back of the envelope calculation is how splits were generated already. But there is big divergence between local, jenkins devbranch and jenkins commit CI runs. So I don't think we can go much further i.e.. timeout is around 10m and there are 3 to 4 splits which should be under the new 4m timeout... > Flaky ViewComplexTest and InsertUpdateIfConditionTest > - > > Key: CASSANDRA-16670 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16670 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-rc2, 4.0, 4.x > > > *ViewComplexTest* > Flaky > [test|https://ci-cassandra.apache.org/job/Cassandra-4.0/43/testReport/junit/org.apache.cassandra.cql3/ViewComplexTest/testPartialDeleteSelectedColumnWithoutFlush_3_/] > *InsertUpdateIfConditionTest* (CASSANDRA-16676) > Fails > [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/testListItem_2__clusterMinVersion_4_0_0_rc2_SNAPSHOT_/] > with a timeout. We can see in the history it takes quite a while in > [CI|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/history/] > _but_ it takes just 1m locally. Probably due to constrained resources. > Looking at the > [individual|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/] > test cases, for compression i.e., we can see 378 at an average of 1s each it > can easily go over the timeout of 240s. Recommendation is to either move to > 'long' section of to raise the timeout for the class for CI. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16690) Flaky NativeAllocatorTest.testBookKeeping
[
https://issues.apache.org/jira/browse/CASSANDRA-16690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352279#comment-17352279
]
Berenguer Blasi commented on CASSANDRA-16690:
-
Stage test reports don't do the fail/pass/fail thing:
https://ci-cassandra.apache.org/job/Cassandra-4.0-test-cdc/47/jdk=jdk_11_latest,label=cassandra,split=8/testReport/junit/org.apache.cassandra.utils.memory/NativeAllocatorTest/testBookKeeping_cdc/
> Flaky NativeAllocatorTest.testBookKeeping
> -
>
> Key: CASSANDRA-16690
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16690
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/52/testReport/junit/org.apache.cassandra.utils.memory/NativeAllocatorTest/testBookKeeping_cdc/]
> {noformat}
> Error Message
> java.lang.AssertionError: expected:<0> but was:<1>
> Stacktrace
> java.util.concurrent.ExecutionException: java.lang.AssertionError:
> expected:<0> but was:<1>
> at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.testBookKeeping(NativeAllocatorTest.java:154)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Caused by: java.lang.AssertionError: expected:<0> but was:<1>
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.lambda$testBookKeeping$2(NativeAllocatorTest.java:131)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16690) Flaky NativeAllocatorTest.testBookKeeping
[
https://issues.apache.org/jira/browse/CASSANDRA-16690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352279#comment-17352279
]
Berenguer Blasi edited comment on CASSANDRA-16690 at 5/27/21, 4:45 AM:
---
Stage test reports don't do the fail/pass/fail thing:
https://ci-cassandra.apache.org/job/Cassandra-4.0-test-cdc/47/jdk=jdk_11_latest,label=cassandra,split=8/testReport/junit/org.apache.cassandra.utils.memory/NativeAllocatorTest/testBookKeeping_cdc/
Did you try looping locally?
was (Author: bereng):
Stage test reports don't do the fail/pass/fail thing:
https://ci-cassandra.apache.org/job/Cassandra-4.0-test-cdc/47/jdk=jdk_11_latest,label=cassandra,split=8/testReport/junit/org.apache.cassandra.utils.memory/NativeAllocatorTest/testBookKeeping_cdc/
> Flaky NativeAllocatorTest.testBookKeeping
> -
>
> Key: CASSANDRA-16690
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16690
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/52/testReport/junit/org.apache.cassandra.utils.memory/NativeAllocatorTest/testBookKeeping_cdc/]
> {noformat}
> Error Message
> java.lang.AssertionError: expected:<0> but was:<1>
> Stacktrace
> java.util.concurrent.ExecutionException: java.lang.AssertionError:
> expected:<0> but was:<1>
> at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.testBookKeeping(NativeAllocatorTest.java:154)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Caused by: java.lang.AssertionError: expected:<0> but was:<1>
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.lambda$testBookKeeping$2(NativeAllocatorTest.java:131)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16684) Flaky MemtableSizeTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352278#comment-17352278
]
Berenguer Blasi commented on CASSANDRA-16684:
-
[~e.dimitrova] if jenkins does the fail/pass/fail dance to you go to the actual
stage test results and the it shows failed always:
https://ci-cassandra.apache.org/job/Cassandra-4.0-test/51/jdk=jdk_11_latest,label=cassandra,split=2/testReport/junit/org.apache.cassandra.cql3/MemtableSizeTest/testSize/
> Flaky MemtableSizeTest
> --
>
> Key: CASSANDRA-16684
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16684
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [MemtableSizeTest|https://ci-cassandra.apache.org/job/Cassandra-4.0/50/testReport/junit/org.apache.cassandra.cql3/MemtableSizeTest/testSize_compression/]
> {noformat}
> Error Message
> Expected heap usage close to 50.085MiB, got 41.294MiB.
> Stacktrace
> junit.framework.AssertionFailedError: Expected heap usage close to 50.085MiB,
> got 41.294MiB.
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-05-18 22:08:42,837 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,840 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,934 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-05-18 22:08:42,956 PlatformDependent0
> ...[truncated 86028 chars]...
> hed transaction log, deleting
> /home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb_txn_flush_a3253f00-b825-11eb-b0ec-cd4f0218a6b5.log
>
> DEBUG [MemtableFlushWriter:2] 2021-05-18 22:08:55,552
> ColumnFamilyStore.java:1197 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-6-big-Data.db')]
> (1 sstables, 4.894KiB), biggest 4.894KiB, smallest 4.894KiB
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16684) Flaky MemtableSizeTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352109#comment-17352109
]
Ekaterina Dimitrova commented on CASSANDRA-16684:
-
/CC [~barnie] as I am running out of ideas with this one...
> Flaky MemtableSizeTest
> --
>
> Key: CASSANDRA-16684
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16684
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [MemtableSizeTest|https://ci-cassandra.apache.org/job/Cassandra-4.0/50/testReport/junit/org.apache.cassandra.cql3/MemtableSizeTest/testSize_compression/]
> {noformat}
> Error Message
> Expected heap usage close to 50.085MiB, got 41.294MiB.
> Stacktrace
> junit.framework.AssertionFailedError: Expected heap usage close to 50.085MiB,
> got 41.294MiB.
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-05-18 22:08:42,837 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,840 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,934 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-05-18 22:08:42,956 PlatformDependent0
> ...[truncated 86028 chars]...
> hed transaction log, deleting
> /home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb_txn_flush_a3253f00-b825-11eb-b0ec-cd4f0218a6b5.log
>
> DEBUG [MemtableFlushWriter:2] 2021-05-18 22:08:55,552
> ColumnFamilyStore.java:1197 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-6-big-Data.db')]
> (1 sstables, 4.894KiB), biggest 4.894KiB, smallest 4.894KiB
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16684) Flaky MemtableSizeTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352105#comment-17352105
]
Ekaterina Dimitrova edited comment on CASSANDRA-16684 at 5/26/21, 10:24 PM:
Alright, it failed three times out of 1000 with Java 11 but this time it shows
we used less heap space... To be precise - Build on Java 8 run with Java 11 -
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/898/workflows/157d2d48-f3be-4709-b3e0-b49c900177a3/jobs/5380
Java 11 build and run is passing 1000 times
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/898/workflows/0bd57270-df52-4572-be97-fc55b05e59d7/jobs/5379
was (Author: e.dimitrova):
Alright, it failed three times out of 1000 with Java 11 but this time it shows
we used less heap space...
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/898/workflows/157d2d48-f3be-4709-b3e0-b49c900177a3/jobs/5380
> Flaky MemtableSizeTest
> --
>
> Key: CASSANDRA-16684
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16684
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [MemtableSizeTest|https://ci-cassandra.apache.org/job/Cassandra-4.0/50/testReport/junit/org.apache.cassandra.cql3/MemtableSizeTest/testSize_compression/]
> {noformat}
> Error Message
> Expected heap usage close to 50.085MiB, got 41.294MiB.
> Stacktrace
> junit.framework.AssertionFailedError: Expected heap usage close to 50.085MiB,
> got 41.294MiB.
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-05-18 22:08:42,837 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,840 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,934 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-05-18 22:08:42,956 PlatformDependent0
> ...[truncated 86028 chars]...
> hed transaction log, deleting
> /home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb_txn_flush_a3253f00-b825-11eb-b0ec-cd4f0218a6b5.log
>
> DEBUG [MemtableFlushWriter:2] 2021-05-18 22:08:55,552
> ColumnFamilyStore.java:1197 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-6-big-Data.db')]
> (1 sstables, 4.894KiB), biggest 4.894KiB, smallest 4.894KiB
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16684) Flaky MemtableSizeTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352105#comment-17352105
]
Ekaterina Dimitrova commented on CASSANDRA-16684:
-
Alright, it failed three times out of 1000 with Java 11 but this time it shows
we used less heap space...
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/898/workflows/157d2d48-f3be-4709-b3e0-b49c900177a3/jobs/5380
> Flaky MemtableSizeTest
> --
>
> Key: CASSANDRA-16684
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16684
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [MemtableSizeTest|https://ci-cassandra.apache.org/job/Cassandra-4.0/50/testReport/junit/org.apache.cassandra.cql3/MemtableSizeTest/testSize_compression/]
> {noformat}
> Error Message
> Expected heap usage close to 50.085MiB, got 41.294MiB.
> Stacktrace
> junit.framework.AssertionFailedError: Expected heap usage close to 50.085MiB,
> got 41.294MiB.
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-05-18 22:08:42,837 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,840 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,934 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-05-18 22:08:42,956 PlatformDependent0
> ...[truncated 86028 chars]...
> hed transaction log, deleting
> /home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb_txn_flush_a3253f00-b825-11eb-b0ec-cd4f0218a6b5.log
>
> DEBUG [MemtableFlushWriter:2] 2021-05-18 22:08:55,552
> ColumnFamilyStore.java:1197 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-6-big-Data.db')]
> (1 sstables, 4.894KiB), biggest 4.894KiB, smallest 4.894KiB
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16690) Flaky NativeAllocatorTest.testBookKeeping
[
https://issues.apache.org/jira/browse/CASSANDRA-16690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352104#comment-17352104
]
Ekaterina Dimitrova commented on CASSANDRA-16690:
-
Please reopen if by chance you see it again
> Flaky NativeAllocatorTest.testBookKeeping
> -
>
> Key: CASSANDRA-16690
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16690
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/52/testReport/junit/org.apache.cassandra.utils.memory/NativeAllocatorTest/testBookKeeping_cdc/]
> {noformat}
> Error Message
> java.lang.AssertionError: expected:<0> but was:<1>
> Stacktrace
> java.util.concurrent.ExecutionException: java.lang.AssertionError:
> expected:<0> but was:<1>
> at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.testBookKeeping(NativeAllocatorTest.java:154)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Caused by: java.lang.AssertionError: expected:<0> but was:<1>
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.lambda$testBookKeeping$2(NativeAllocatorTest.java:131)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16690) Flaky NativeAllocatorTest.testBookKeeping
[
https://issues.apache.org/jira/browse/CASSANDRA-16690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352103#comment-17352103
]
Ekaterina Dimitrova commented on CASSANDRA-16690:
-
It shows again passed when I open the link. If I search in the runs I found it
failed with cdc once.
But then I ran it with Java 8 and Java 11 1000 times and nothing so I close as
not reproducible.
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/903/workflows/aeb8aea1-92d5-445a-a257-21c2295a5681/jobs/5378
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/903/workflows/35333c7f-0548-4e54-b372-f6d861ffc10d/jobs/5373
https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/903/workflows/aeb8aea1-92d5-445a-a257-21c2295a5681/jobs/5375
> Flaky NativeAllocatorTest.testBookKeeping
> -
>
> Key: CASSANDRA-16690
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16690
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/52/testReport/junit/org.apache.cassandra.utils.memory/NativeAllocatorTest/testBookKeeping_cdc/]
> {noformat}
> Error Message
> java.lang.AssertionError: expected:<0> but was:<1>
> Stacktrace
> java.util.concurrent.ExecutionException: java.lang.AssertionError:
> expected:<0> but was:<1>
> at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.testBookKeeping(NativeAllocatorTest.java:154)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Caused by: java.lang.AssertionError: expected:<0> but was:<1>
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.lambda$testBookKeeping$2(NativeAllocatorTest.java:131)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16690) Flaky NativeAllocatorTest.testBookKeeping
[
https://issues.apache.org/jira/browse/CASSANDRA-16690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16690:
Resolution: Cannot Reproduce
Status: Resolved (was: Open)
> Flaky NativeAllocatorTest.testBookKeeping
> -
>
> Key: CASSANDRA-16690
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16690
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/52/testReport/junit/org.apache.cassandra.utils.memory/NativeAllocatorTest/testBookKeeping_cdc/]
> {noformat}
> Error Message
> java.lang.AssertionError: expected:<0> but was:<1>
> Stacktrace
> java.util.concurrent.ExecutionException: java.lang.AssertionError:
> expected:<0> but was:<1>
> at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
> at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191)
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.testBookKeeping(NativeAllocatorTest.java:154)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Caused by: java.lang.AssertionError: expected:<0> but was:<1>
> at
> org.apache.cassandra.utils.memory.NativeAllocatorTest.lambda$testBookKeeping$2(NativeAllocatorTest.java:131)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at java.base/java.lang.Thread.run(Thread.java:834)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16696) pylib requirements.txt should demand six >=1.12.0 rather than 0.12.0
[
https://issues.apache.org/jira/browse/CASSANDRA-16696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16696:
-
Resolution: Fixed
Status: Resolved (was: Open)
I ninja'd six >=1.12.0 in 4.0/trunk and cassandra-dtest. If we need it back
further let's discuss in a new ticket.
> pylib requirements.txt should demand six >=1.12.0 rather than 0.12.0
>
>
> Key: CASSANDRA-16696
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16696
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Tomasz Lasica
>Assignee: Tomasz Lasica
>Priority: Low
> Fix For: 4.0-rc, 4.0.x
>
>
> In 4.0 min six version is explicitly specified here
> [https://github.com/apache/cassandra/blob/6c8ab5b6b41830ac0d0ee381a7669b06ffd5b43a/pylib/requirements.txt#L5]
> but it is probably a typo: \{{ six>=0.12.0 }}
> and should be {{>=1.12.0}}, version that ensures that "ensure_text" is
> present:
> see six PR: [https://github.com/benjaminp/six/pull/204]
> It can lead to {{import}} problems with pylib and in effect to problems with
> the cqlsh tests.
> Proposed fix:
> # request six>=1.12.0 in pylib requirements.txt on all C* branches
> # request six>=1.12.0 in dtest requirements.txt
>
> C* versions before 4.0 does not specify six version at all, which I suspect
> can be also improved.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16696) pylib requirements.txt should demand six >=1.12.0 rather than 0.12.0
[
https://issues.apache.org/jira/browse/CASSANDRA-16696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16696:
-
Fix Version/s: (was: 4.0.x)
(was: 4.0-rc)
4.1
4.0
4.0-rc2
> pylib requirements.txt should demand six >=1.12.0 rather than 0.12.0
>
>
> Key: CASSANDRA-16696
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16696
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Tomasz Lasica
>Assignee: Tomasz Lasica
>Priority: Low
> Fix For: 4.0-rc2, 4.0, 4.1
>
>
> In 4.0 min six version is explicitly specified here
> [https://github.com/apache/cassandra/blob/6c8ab5b6b41830ac0d0ee381a7669b06ffd5b43a/pylib/requirements.txt#L5]
> but it is probably a typo: \{{ six>=0.12.0 }}
> and should be {{>=1.12.0}}, version that ensures that "ensure_text" is
> present:
> see six PR: [https://github.com/benjaminp/six/pull/204]
> It can lead to {{import}} problems with pylib and in effect to problems with
> the cqlsh tests.
> Proposed fix:
> # request six>=1.12.0 in pylib requirements.txt on all C* branches
> # request six>=1.12.0 in dtest requirements.txt
>
> C* versions before 4.0 does not specify six version at all, which I suspect
> can be also improved.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated: ninja fix six typo to be six >=1.12.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-4.0 by this push: new cfc8ef3 ninja fix six typo to be six >=1.12.0 cfc8ef3 is described below commit cfc8ef3313efd6913b02433da0f0a4d0af2bc130 Author: Brandon Williams AuthorDate: Wed May 26 16:50:14 2021 -0500 ninja fix six typo to be six >=1.12.0 --- pylib/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pylib/requirements.txt b/pylib/requirements.txt index cdfa566..17d4ab0 100644 --- a/pylib/requirements.txt +++ b/pylib/requirements.txt @@ -2,7 +2,7 @@ # cythonizing the driver, perhaps only on old pips. # http://datastax.github.io/python-driver/installation.html#cython-based-extensions futures -six>=0.12.0 +six>=1.12.0 -e git+https://github.com/datastax/python-driver.git@cassandra-test#egg=cassandra-driver # Used ccm version is tracked by cassandra-test branch in ccm repo. Please create a PR there for fixes or upgrades to new releases. -e git+https://github.com/riptano/ccm.git@cassandra-test#egg=ccm - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated: ninja fix six typo to be six >=1.12.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/trunk by this push: new 7e1afa1 ninja fix six typo to be six >=1.12.0 7e1afa1 is described below commit 7e1afa1fe60242d2252485b6225b7a59762c3741 Author: Brandon Williams AuthorDate: Wed May 26 16:50:14 2021 -0500 ninja fix six typo to be six >=1.12.0 --- pylib/requirements.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pylib/requirements.txt b/pylib/requirements.txt index cdfa566..17d4ab0 100644 --- a/pylib/requirements.txt +++ b/pylib/requirements.txt @@ -2,7 +2,7 @@ # cythonizing the driver, perhaps only on old pips. # http://datastax.github.io/python-driver/installation.html#cython-based-extensions futures -six>=0.12.0 +six>=1.12.0 -e git+https://github.com/datastax/python-driver.git@cassandra-test#egg=cassandra-driver # Used ccm version is tracked by cassandra-test branch in ccm repo. Please create a PR there for fixes or upgrades to new releases. -e git+https://github.com/riptano/ccm.git@cassandra-test#egg=ccm - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-dtest] branch trunk updated: ninja fix six >=1.12.0
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra-dtest.git The following commit(s) were added to refs/heads/trunk by this push: new 363ebdb ninja fix six >=1.12.0 363ebdb is described below commit 363ebdbb644253c2ab142066b609910bfc07510e Author: Brandon Williams AuthorDate: Wed May 26 16:51:39 2021 -0500 ninja fix six >=1.12.0 --- requirements.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/requirements.txt b/requirements.txt index 9754239..375cada 100644 --- a/requirements.txt +++ b/requirements.txt @@ -18,6 +18,7 @@ pytest-repeat parse pycodestyle psutil +six>=1.12.0 thrift==0.10.0 netifaces beautifulsoup4 - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16696) pylib requirements.txt should demand six >=1.12.0 rather than 0.12.0
[
https://issues.apache.org/jira/browse/CASSANDRA-16696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352079#comment-17352079
]
Ekaterina Dimitrova commented on CASSANDRA-16696:
-
I think six is added only in 4.0 and trunk because we need it for compatibility
python2-python3. As we don't support python 3 in the previous versions, we
don't need it.
> pylib requirements.txt should demand six >=1.12.0 rather than 0.12.0
>
>
> Key: CASSANDRA-16696
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16696
> Project: Cassandra
> Issue Type: Improvement
> Components: Test/dtest/python
>Reporter: Tomasz Lasica
>Assignee: Tomasz Lasica
>Priority: Low
> Fix For: 4.0-rc, 4.0.x
>
>
> In 4.0 min six version is explicitly specified here
> [https://github.com/apache/cassandra/blob/6c8ab5b6b41830ac0d0ee381a7669b06ffd5b43a/pylib/requirements.txt#L5]
> but it is probably a typo: \{{ six>=0.12.0 }}
> and should be {{>=1.12.0}}, version that ensures that "ensure_text" is
> present:
> see six PR: [https://github.com/benjaminp/six/pull/204]
> It can lead to {{import}} problems with pylib and in effect to problems with
> the cqlsh tests.
> Proposed fix:
> # request six>=1.12.0 in pylib requirements.txt on all C* branches
> # request six>=1.12.0 in dtest requirements.txt
>
> C* versions before 4.0 does not specify six version at all, which I suspect
> can be also improved.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated (f4ab8cc -> 55b4b8d)
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a change to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git. from f4ab8cc Keep python driver in artifacts. add 55b4b8d Ninja fix typo in commit log archive page No new revisions were added by this update. Summary of changes: doc/source/configuration/cass_cl_archive_file.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit f8f94c2f674fe61a280a4e72bcc84a283430632d Merge: 855dcad 55b4b8d Author: Ekaterina Dimitrova AuthorDate: Wed May 26 16:45:45 2021 -0400 Merge branch 'cassandra-4.0' into trunk doc/source/configuration/cass_cl_archive_file.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (855dcad -> f8f94c2)
This is an automated email from the ASF dual-hosted git repository. edimitrova pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 855dcad Merge branch 'cassandra-4.0' into trunk add 55b4b8d Ninja fix typo in commit log archive page new f8f94c2 Merge branch 'cassandra-4.0' into trunk The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: doc/source/configuration/cass_cl_archive_file.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16684) Flaky MemtableSizeTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352041#comment-17352041
]
Ekaterina Dimitrova edited comment on CASSANDRA-16684 at 5/26/21, 8:22 PM:
---
[~bereng] now both links show passed and I ran it [1000
times|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/898/workflows/157d2d48-f3be-4709-b3e0-b49c900177a3/jobs/5340/artifacts]
and it succeeded. I am puzzled I saw it failing in CI too, but now the
status is changed
was (Author: e.dimitrova):
[~bereng] now both links show passed and I ran it [1000
times|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/896/workflows/6271ad8f-40cd-4cff-8ae5-63d0cec09565/jobs/5327]
and it succeeded. I am puzzled I saw it failing in CI too, but now the
status is changed
> Flaky MemtableSizeTest
> --
>
> Key: CASSANDRA-16684
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16684
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [MemtableSizeTest|https://ci-cassandra.apache.org/job/Cassandra-4.0/50/testReport/junit/org.apache.cassandra.cql3/MemtableSizeTest/testSize_compression/]
> {noformat}
> Error Message
> Expected heap usage close to 50.085MiB, got 41.294MiB.
> Stacktrace
> junit.framework.AssertionFailedError: Expected heap usage close to 50.085MiB,
> got 41.294MiB.
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-05-18 22:08:42,837 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,840 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,934 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-05-18 22:08:42,956 PlatformDependent0
> ...[truncated 86028 chars]...
> hed transaction log, deleting
> /home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb_txn_flush_a3253f00-b825-11eb-b0ec-cd4f0218a6b5.log
>
> DEBUG [MemtableFlushWriter:2] 2021-05-18 22:08:55,552
> ColumnFamilyStore.java:1197 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-6-big-Data.db')]
> (1 sstables, 4.894KiB), biggest 4.894KiB, smallest 4.894KiB
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16689) Flaky LeaveAndBootstrapTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-16689:
Assignee: Brandon Williams
> Flaky LeaveAndBootstrapTest
> ---
>
> Key: CASSANDRA-16689
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16689
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Failing in a circle run
> [here|https://app.circleci.com/pipelines/github/bereng/cassandra/309/workflows/a645b956-dcd7-431e-b109-7857af3c523f/jobs/2937]
> {noformat}
> Testcase:
> testStateJumpToNormal(org.apache.cassandra.service.LeaveAndBootstrapTest):
> Caused an ERROR
> [junit-timeout] null
> [junit-timeout] java.lang.NullPointerException
> [junit-timeout] at
> org.apache.cassandra.service.StorageService.updatePeerInfo(StorageService.java:2418)
> [junit-timeout] at
> org.apache.cassandra.service.StorageService.handleStateNormal(StorageService.java:2756)
> [junit-timeout] at
> org.apache.cassandra.service.StorageService.onChange(StorageService.java:2299)
> [junit-timeout] at
> org.apache.cassandra.Util.createInitialRing(Util.java:236)
> [junit-timeout] at
> org.apache.cassandra.service.LeaveAndBootstrapTest.testStateJumpToNormal(LeaveAndBootstrapTest.java:550)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16684) Flaky MemtableSizeTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352041#comment-17352041
]
Ekaterina Dimitrova commented on CASSANDRA-16684:
-
[~bereng] now both links show passed and I ran it [1000
times|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/896/workflows/6271ad8f-40cd-4cff-8ae5-63d0cec09565/jobs/5327]
and it succeeded. I am puzzled I saw it failing in CI too, but now the
status is changed
> Flaky MemtableSizeTest
> --
>
> Key: CASSANDRA-16684
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16684
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Berenguer Blasi
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.x
>
>
> Flaky
> [MemtableSizeTest|https://ci-cassandra.apache.org/job/Cassandra-4.0/50/testReport/junit/org.apache.cassandra.cql3/MemtableSizeTest/testSize_compression/]
> {noformat}
> Error Message
> Expected heap usage close to 50.085MiB, got 41.294MiB.
> Stacktrace
> junit.framework.AssertionFailedError: Expected heap usage close to 50.085MiB,
> got 41.294MiB.
> at
> org.apache.cassandra.cql3.MemtableSizeTest.testSize(MemtableSizeTest.java:121)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> Standard Output
> INFO [main] 2021-05-18 22:08:42,837 YamlConfigurationLoader.java:93 -
> Configuration location:
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,840 YamlConfigurationLoader.java:112 -
> Loading settings from
> file:home/cassandra/cassandra/build/test/cassandra.compressed.yaml
> DEBUG [main] 2021-05-18 22:08:42,934 InternalLoggerFactory.java:63 - Using
> SLF4J as the default logging framework
> DEBUG [main] 2021-05-18 22:08:42,956 PlatformDependent0
> ...[truncated 86028 chars]...
> hed transaction log, deleting
> /home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb_txn_flush_a3253f00-b825-11eb-b0ec-cd4f0218a6b5.log
>
> DEBUG [MemtableFlushWriter:2] 2021-05-18 22:08:55,552
> ColumnFamilyStore.java:1197 - Flushed to
> [BigTableReader(path='/home/cassandra/cassandra/build/test/cassandra/data/system_schema/keyspaces-abac5682dea631c5b535b3d6cffd0fb6/nb-6-big-Data.db')]
> (1 sstables, 4.894KiB), biggest 4.894KiB, smallest 4.894KiB
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16679) HintedHandoffAddRemoveNodesTest is failing
[
https://issues.apache.org/jira/browse/CASSANDRA-16679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352034#comment-17352034
]
Ekaterina Dimitrova commented on CASSANDRA-16679:
-
Node 2:
{code:java}
INFO [node2_GossipStage:1] node2 2021-05-26 16:14:07,666 InetAddress
/127.0.0.4:7012 is now DOWN
DEBUG [node2_GossipStage:1] node2 2021-05-26 16:14:07,667 Forcing conviction of
/127.0.0.4:7012
INFO [node2_Messaging-EventLoop-3-7] node2 2021-05-26 16:14:07,673
/127.0.0.2:7012(/127.0.0.1:50938)->/127.0.0.4:7012-URGENT_MESSAGES-5627f198
successfully connected, version = 12, framing = CRC, encryption = unencrypted
DEBUG [node2_GossipStage:1] node2 2021-05-26 16:14:07,676 removing expire time
for endpoint : /127.0.0.4:7012
INFO [node2_GossipStage:1] node2 2021-05-26 16:14:07,676 InetAddress
/127.0.0.4:7012 is now UP
DEBUG [node2_GossipStage:1] node2 2021-05-26 16:14:07,676 removing expire time
for endpoint : /127.0.0.4:7012
INFO [node2_GossipStage:1] node2 2021-05-26 16:14:07,676 InetAddress
/127.0.0.4:7012 is now UP
{code}
This is from node 4:
{code:java}
INFO [node4_isolatedExecutor:3] node4 2021-05-26 16:14:07,660 Announcing
shutdown
DEBUG [node4_isolatedExecutor:3] node4 2021-05-26 16:14:07,660 Node
/127.0.0.4:7012 state shutdown, token [9223372036854775801]
INFO [node4_isolatedExecutor:6] node4 2021-05-26 16:14:07,660 Paused hints
dispatch
INFO [node4_isolatedExecutor:3] node4 2021-05-26 16:14:07,660 Node
/127.0.0.4:7012 state jump to shutdown
DEBUG [node4_isolatedExecutor:3] node4 2021-05-26 16:14:07,661 Node
/127.0.0.4:7012 state shutdown, token [9223372036854775801]
INFO [node4_isolatedExecutor:3] node4 2021-05-26 16:14:07,661 Node
/127.0.0.4:7012 state jump to shutdown
INFO [node4_Messaging-EventLoop-3-19] node4 2021-05-26 16:14:07,673
/127.0.0.2:7012(/127.0.0.1:50938)->/127.0.0.4:7012-URGENT_MESSAGES-e48b31a6
messaging connection established, version = 12, framing = CRC, encryption =
unencrypted
INFO [node4_Messaging-EventLoop-3-20] node4 2021-05-26 16:14:08,604
/127.0.0.1:7012(/127.0.0.1:51090)->/127.0.0.4:7012-URGENT_MESSAGES-559580c8
messaging connection established, version = 12, framing = CRC, encryption =
unencrypted
INFO [node4_isolatedExecutor:17] node4 2021-05-26 16:14:09,666 Waiting for
messaging service to quiesce{code}
> HintedHandoffAddRemoveNodesTest is failing
> --
>
> Key: CASSANDRA-16679
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16679
> Project: Cassandra
> Issue Type: Bug
> Components: CI
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.0-rc
>
>
> https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.distributed.test/HintedHandoffAddRemoveNodesTest/shouldStreamHintsDuringDecommission/
> Java 8
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/464/workflows/888e47fb-e432-47f2-97df-c34a0d33753a/jobs/4104]
>
> and Java 11
>
> [https://app.circleci.com/pipelines/github/adelapena/cassandra/464/workflows/ce0f0690-e488-4b5b-ab82-ce92a2f336d8/jobs/4105]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16677) Fix flaky ConnectionTest.testMessageDeliveryOnReconnect
[
https://issues.apache.org/jira/browse/CASSANDRA-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352030#comment-17352030
]
Brandon Williams edited comment on CASSANDRA-16677 at 5/26/21, 7:23 PM:
I'm giving up on this for now, as it can only damage my calm further to
continue.
What I've found is that sometimes you will see a stack that seems to indicate
the channel was already closed:
{noformat}
[junit-timeout] WARN
[Messaging-OUT-/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES] 2021-05-26
16:38:31,164 OutboundConnection.java:492 -
/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES-[no-channel] dropping message
of type _TEST_1 due to error
[junit-timeout] org.apache.cassandra.net.AsyncChannelOutputPlus$FlushException:
This output stream is in an unsafe state after an asynchronous flush failed
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.propagateFailedFlush(AsyncChannelOutputPlus.java:209)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.waitUntilFlushed(AsyncChannelOutputPlus.java:166)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.flush(AsyncChannelOutputPlus.java:238)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.close(AsyncChannelOutputPlus.java:259)
[junit-timeout] at
org.apache.cassandra.net.AsyncMessageOutputPlus.close(AsyncMessageOutputPlus.java:117)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.doRun(OutboundConnection.java:1002)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$Delivery.run(OutboundConnection.java:691)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.run(OutboundConnection.java:960)
[junit-timeout] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[junit-timeout] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[junit-timeout] at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[junit-timeout] at java.lang.Thread.run(Thread.java:748)
{noformat}
if you add a test for the channel being open before this, it passes. Other
times the test will fail in what appears to be the same manner, but there will
be no stacktrace at all. Most of the failures occur with LARGE_MESSAGES, but
given enough attempts there is occasionally one in SMALL_MESSAGES.
Then there is the unique stack that Berenguer linked, which I have yet to
encounter myself. It is odd too, in that according to it both small and large
messages are expecting 30 bytes and only getting 29, but all my debugging shows
29 bytes working just fine for large messages, and 11 for small (where the
stack wants 14, receiving 13.)
was (Author: brandon.williams):
I'm giving up on this for now, as it can only damage my calm further to
continue.
What I've found is that sometimes you will see a stack that seems to indicate
the channel was already closed:
{noformat}
[junit-timeout] WARN
[Messaging-OUT-/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES] 2021-05-26
16:38:31,164 OutboundConnection.java:492 -
/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES-[no-channel] dropping message
of type _TEST_1 due to error
[junit-timeout] org.apache.cassandra.net.AsyncChannelOutputPlus$FlushException:
This output stream is in an unsafe state after an asynchronous flush failed
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.propagateFailedFlush(AsyncChannelOutputPlus.java:209)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.waitUntilFlushed(AsyncChannelOutputPlus.java:166)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.flush(AsyncChannelOutputPlus.java:238)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.close(AsyncChannelOutputPlus.java:259)
[junit-timeout] at
org.apache.cassandra.net.AsyncMessageOutputPlus.close(AsyncMessageOutputPlus.java:117)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.doRun(OutboundConnection.java:1002)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$Delivery.run(OutboundConnection.java:691)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.run(OutboundConnection.java:960)
[junit-timeout] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[junit-timeout] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[junit-timeout] at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[junit-timeout] at java.lang.Thread.run(Thread.java:748)
{noformat}
if you
[jira] [Commented] (CASSANDRA-16677) Fix flaky ConnectionTest.testMessageDeliveryOnReconnect
[
https://issues.apache.org/jira/browse/CASSANDRA-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352030#comment-17352030
]
Brandon Williams commented on CASSANDRA-16677:
--
I'm giving up on this for now, as it can only damage my calm further to
continue.
What I've found is that sometimes you will see a stack that seems to indicate
the channel was already closed:
{noformat}
[junit-timeout] WARN
[Messaging-OUT-/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES] 2021-05-26
16:38:31,164 OutboundConnection.java:492 -
/127.0.0.1:7012->/127.0.0.1:7012-LARGE_MESSAGES-[no-channel] dropping message
of type _TEST_1 due to error
[junit-timeout] org.apache.cassandra.net.AsyncChannelOutputPlus$FlushException:
This output stream is in an unsafe state after an asynchronous flush failed
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.propagateFailedFlush(AsyncChannelOutputPlus.java:209)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.waitUntilFlushed(AsyncChannelOutputPlus.java:166)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.flush(AsyncChannelOutputPlus.java:238)
[junit-timeout] at
org.apache.cassandra.net.AsyncChannelOutputPlus.close(AsyncChannelOutputPlus.java:259)
[junit-timeout] at
org.apache.cassandra.net.AsyncMessageOutputPlus.close(AsyncMessageOutputPlus.java:117)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.doRun(OutboundConnection.java:1002)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$Delivery.run(OutboundConnection.java:691)
[junit-timeout] at
org.apache.cassandra.net.OutboundConnection$LargeMessageDelivery.run(OutboundConnection.java:960)
[junit-timeout] at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
[junit-timeout] at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
[junit-timeout] at
io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
[junit-timeout] at java.lang.Thread.run(Thread.java:748)
{noformat}
if you add a test for the channel being open before this, it passes. Other
times the test will fail in what appears to be the same manner, but there will
be no stacktrace at all. Most of the failures occur with LARGE_MESSAGES, but
given enough attemps there is occasionally one in SMALL_MESSAGES.
Then there is the unique stack that Berenguer linked, which I have yet to
encounter myself. It is odd too, in that according to it both small and large
messages are expecting 30 bytes and only getting 29, but all my debugging shows
29 bytes working just fine for large messages, and 11 for small (where the
stack wants 14, receiving 13.)
> Fix flaky ConnectionTest.testMessageDeliveryOnReconnect
> ---
>
> Key: CASSANDRA-16677
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16677
> Project: Cassandra
> Issue Type: Bug
> Components: Messaging/Internode
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
>
> https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_compression/
> https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/cf7dcec6-612c-45d1-8471-623bde481dca/jobs/4069
> https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/b750cd38-0263-4b5e-9bb8-a8be98214378/jobs/4065
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16677) Fix flaky ConnectionTest.testMessageDeliveryOnReconnect
[ https://issues.apache.org/jira/browse/CASSANDRA-16677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams reassigned CASSANDRA-16677: Assignee: (was: Brandon Williams) > Fix flaky ConnectionTest.testMessageDeliveryOnReconnect > --- > > Key: CASSANDRA-16677 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16677 > Project: Cassandra > Issue Type: Bug > Components: Messaging/Internode >Reporter: Brandon Williams >Priority: Normal > > https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.net/ConnectionTest/testMessageDeliveryOnReconnect_compression/ > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/cf7dcec6-612c-45d1-8471-623bde481dca/jobs/4069 > https://app.circleci.com/pipelines/github/adelapena/cassandra/460/workflows/b750cd38-0263-4b5e-9bb8-a8be98214378/jobs/4065 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16700:
-
Resolution: Fixed
Status: Resolved (was: Open)
Not very complicated after all, so done in
https://github.com/apache/cassandra/commit/f4ab8cce1e4f517406c1343d369326916586db67.
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-rc
>
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16700:
-
Fix Version/s: (was: 4.0-rc)
4.1
4.0
4.0-rc2
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-rc2, 4.0, 4.1
>
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16700:
-
Status: Open (was: Patch Available)
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-rc
>
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16700:
-
Test and Documentation Plan: manual inspection
Status: Patch Available (was: In Progress)
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-rc
>
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] 01/01: Merge branch 'cassandra-4.0' into trunk
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit 855dcad75b39dbe9a1db42c75274d1f81cc53c7e Merge: 1e19a61 f4ab8cc Author: Brandon Williams AuthorDate: Wed May 26 13:57:40 2021 -0500 Merge branch 'cassandra-4.0' into trunk CHANGES.txt | 1 + build.xml | 5 + 2 files changed, 6 insertions(+) diff --cc CHANGES.txt index b3e6853,90d5c08..f7927e5 --- a/CHANGES.txt +++ b/CHANGES.txt @@@ -1,6 -1,5 +1,7 @@@ -4.0-rc2 +4.1 + * GossiperTest.testHasVersion3Nodes didn't take into account trunk version changes, fixed to rely on latest version (CASSANDRA-16651) +Merged from 4.0: + * Keep python driver in artifacts (CASSANDRA-16700) * Improve AuditLogging documentation and logback.xml(CASSANDRA-16682) * Spin up SEPWorker threads whenever we grow the number of work permits(CASSANDRA-16668) * Add a warning to cqlsh 6.0.0 that DESCRIBE does not work with a Cassandra 3.x servers (CASSANDRA-16652) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-4.0 updated: Keep python driver in artifacts.
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a commit to branch cassandra-4.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git The following commit(s) were added to refs/heads/cassandra-4.0 by this push: new f4ab8cc Keep python driver in artifacts. f4ab8cc is described below commit f4ab8cce1e4f517406c1343d369326916586db67 Author: Brandon Williams AuthorDate: Wed May 26 13:56:48 2021 -0500 Keep python driver in artifacts. Patch by brandonwilliams; approved by mck for CASSANDRA-16700 --- CHANGES.txt | 1 + build.xml | 5 + 2 files changed, 6 insertions(+) diff --git a/CHANGES.txt b/CHANGES.txt index e2305d1..90d5c08 100644 --- a/CHANGES.txt +++ b/CHANGES.txt @@ -1,4 +1,5 @@ 4.0-rc2 + * Keep python driver in artifacts (CASSANDRA-16700) * Improve AuditLogging documentation and logback.xml(CASSANDRA-16682) * Spin up SEPWorker threads whenever we grow the number of work permits(CASSANDRA-16668) * Add a warning to cqlsh 6.0.0 that DESCRIBE does not work with a Cassandra 3.x servers (CASSANDRA-16652) diff --git a/build.xml b/build.xml index ed42fb2..9198410 100644 --- a/build.xml +++ b/build.xml @@ -1185,6 +1185,11 @@ + + + + + - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (1e19a61 -> 855dcad)
This is an automated email from the ASF dual-hosted git repository. brandonwilliams pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git. from 1e19a61 Merge branch 'cassandra-4.0' into trunk new f4ab8cc Keep python driver in artifacts. new 855dcad Merge branch 'cassandra-4.0' into trunk The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: CHANGES.txt | 1 + build.xml | 5 + 2 files changed, 6 insertions(+) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16679) HintedHandoffAddRemoveNodesTest is failing
[ https://issues.apache.org/jira/browse/CASSANDRA-16679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17352019#comment-17352019 ] Ekaterina Dimitrova commented on CASSANDRA-16679: - After experimenting more with this one I think this is probably some very tiny race around the in-jvm tests framework. If I remove node 4 never to get back up, I still can see in the logs of node 2 that node 4 goes down and then a connection is established between node 2 and node4 and node 4 is marked immediately up in the logs of node 2... Then I looped the original python dtest 500 times and it succeeded. My suggestion is to fix this issue but not to block the release on it. [~ifesdjeen], [~blerer], [~maedhroz], any thoughts? > HintedHandoffAddRemoveNodesTest is failing > -- > > Key: CASSANDRA-16679 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16679 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.0-rc > > > https://ci-cassandra.apache.org/job/Cassandra-devbranch/785/testReport/junit/org.apache.cassandra.distributed.test/HintedHandoffAddRemoveNodesTest/shouldStreamHintsDuringDecommission/ > Java 8 > [https://app.circleci.com/pipelines/github/adelapena/cassandra/464/workflows/888e47fb-e432-47f2-97df-c34a0d33753a/jobs/4104] > > and Java 11 > > [https://app.circleci.com/pipelines/github/adelapena/cassandra/464/workflows/ce0f0690-e488-4b5b-ab82-ce92a2f336d8/jobs/4105] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16681) org.apache.cassandra.utils.memory.LongBufferPoolTest - tests are flaky
[ https://issues.apache.org/jira/browse/CASSANDRA-16681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351980#comment-17351980 ] Adam Holmberg commented on CASSANDRA-16681: --- Although I still think there is a race as described, more troubleshooting has indicated that it is not the cause for this assertion error most times. It's happening earlier on in the test when the threads would not be exiting. When it does happen, there is always only a single tracked chunk that has not been recycled a given time interval. It appears that the chunk is not being acquired or cycled in any way after entering this state. Still digging on it, but if anyone with more knowledge in the area wants to take a look, they are welcome. > org.apache.cassandra.utils.memory.LongBufferPoolTest - tests are flaky > -- > > Key: CASSANDRA-16681 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16681 > Project: Cassandra > Issue Type: Bug > Components: CI >Reporter: Ekaterina Dimitrova >Assignee: Adam Holmberg >Priority: Normal > Fix For: 4.0, 4.0-rc > > Time Spent: 20m > Remaining Estimate: 0h > > Jenkins history: > [https://jenkins-cm4.apache.org/job/Cassandra-4.0/50/testReport/junit/org.apache.cassandra.utils.memory/LongBufferPoolTest/testPoolAllocateWithRecyclePartially/history/] > Fails being run in a loop in CircleCI: > https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/844/workflows/945011f4-00ac-4678-89f6-5c0db0a40169/jobs/5008 > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351964#comment-17351964
]
Brandon Williams commented on CASSANDRA-16700:
--
The line removing the driver
https://github.com/apache/cassandra/blob/cassandra-4.0/build.xml#L1167 is also
excluding the rest of lib, so this won't be a simple single line removal. I'll
post a patch shortly.
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-rc
>
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16700:
-
Fix Version/s: 4.0-rc
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 4.0-rc
>
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams reassigned CASSANDRA-16700:
Assignee: Brandon Williams
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Assignee: Brandon Williams
>Priority: Normal
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351933#comment-17351933
]
Michael Semb Wever commented on CASSANDRA-16700:
bq. Should we just ninja out the removal then?
+1
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Priority: Normal
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351913#comment-17351913
]
Brandon Williams commented on CASSANDRA-16700:
--
Should we just ninja out the removal then?
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Priority: Normal
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16687) Support upgrade tests in CircleCI multiplexer
[
https://issues.apache.org/jira/browse/CASSANDRA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351904#comment-17351904
]
Andres de la Peña commented on CASSANDRA-16687:
---
Great, thanks. I'll prepare the PRs for the other branches.
> Support upgrade tests in CircleCI multiplexer
> -
>
> Key: CASSANDRA-16687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16687
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The CircleCI jobs for running a test repeatedly added by CASSANDRA-16625
> don't support upgrade tests. In the case of Python upgrade dtests we only
> need the {{--execute-upgrade-tests}} when calling {{pytest}}. For Java
> upgrade tests we need to build the dtest jars before running the repeated
> tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351902#comment-17351902
]
Michael Semb Wever commented on CASSANDRA-16700:
I'm thinking we leave the python dependency in the source artefact.
On the last board report we were told that the policy has been updated.
It currently stands as…
{quote}
SOURCE PACKAGES
Every ASF release MUST contain one or more source packages, which MUST be
sufficient for a user to build and test the release provided they have access
to the appropriate platform and tools. A source release SHOULD not contain
compiled code.
{quote}
Those python zip files are not compiled. And it only says "SHOULD not"
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Priority: Normal
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351888#comment-17351888
]
Brandon Williams commented on CASSANDRA-16700:
--
[~mck] shouldn't we at least let a user with a source dist pull in the driver
when they build with ant?
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Priority: Normal
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16700) Python driver dependency missing
[
https://issues.apache.org/jira/browse/CASSANDRA-16700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-16700:
-
Bug Category: Parent values: Availability(12983)
Complexity: Low Hanging Fruit
Discovered By: User Report
Severity: Normal
Status: Open (was: Triage Needed)
> Python driver dependency missing
>
>
> Key: CASSANDRA-16700
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
> Project: Cassandra
> Issue Type: Bug
> Components: Dependencies
>Reporter: Angelo Polo
>Priority: Normal
>
> Cqlsh depends on the python driver, which is not included in the downloaded
> dependencies.
> {noformat}
> $ bin/cqlsh
> Python Cassandra driver not installed, or not on PYTHONPATH.
> You might try "pip install cassandra-driver".
> Python: /usr/local/bin/python3
> Module load path:
> ['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
> '/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
> '/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
> '/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
> '/usr/local/lib/python3.7/site-packages']
> Error: No module named 'cassandra'
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-16700) Python driver dependency missing
Angelo Polo created CASSANDRA-16700:
---
Summary: Python driver dependency missing
Key: CASSANDRA-16700
URL: https://issues.apache.org/jira/browse/CASSANDRA-16700
Project: Cassandra
Issue Type: Bug
Components: Dependencies
Reporter: Angelo Polo
Cqlsh depends on the python driver, which is not included in the downloaded
dependencies.
{noformat}
$ bin/cqlsh
Python Cassandra driver not installed, or not on PYTHONPATH.
You might try "pip install cassandra-driver".
Python: /usr/local/bin/python3
Module load path:
['/usr/local/share/java/cassandra/bin/../lib/geomet-0.1.0.zip',
'/usr/local/share/java/cassandra/bin/../lib/six-1.12.0-py2.py3-none-any.zip',
'/usr/local/share/java/cassandra/bin/../lib/futures-2.1.6-py2.py3-none-any.zip',
'/usr/local/share/java/cassandra/bin', '/usr/local/lib/python37.zip',
'/usr/local/lib/python3.7', '/usr/local/lib/python3.7/lib-dynload',
'/usr/local/lib/python3.7/site-packages']
Error: No module named 'cassandra'
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16698) Security vulnerability CVE-2019-9518 for Netty
[ https://issues.apache.org/jira/browse/CASSANDRA-16698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-16698: - Resolution: Not A Problem Status: Resolved (was: Triage Needed) Cassandra does not use an HTTP transport. > Security vulnerability CVE-2019-9518 for Netty > -- > > Key: CASSANDRA-16698 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16698 > Project: Cassandra > Issue Type: Bug >Reporter: Ethern Su >Priority: Normal > > *Cassandra Version: 3.11.10* > *Description :* > *Severity:* NVD CVSS:3.1 7.5 High > *Affecting Package*: netty-all 4.0.44.Final > *Source:* National Vulnerability Database > *Explanation from NVD:* Some HTTP/2 implementations are vulnerable to a flood > of empty frames, potentially leading to a denial of service. The attacker > sends a stream of frames with an empty payload and without the end-of-stream > flag. These frames can be DATA, HEADERS, CONTINUATION and/or PUSH_PROMISE. > The peer spends time processing each frame disproportionate to attack > bandwidth. This can consume excess CPU. > *Recommendation:* Upgrade package io.netty#netty-all to version 4.1.39.Final > or above. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16699) Security vulnerability CVE-2020-7238 for Netty
[ https://issues.apache.org/jira/browse/CASSANDRA-16699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-16699: - Resolution: Not A Problem Status: Resolved (was: Triage Needed) Cassandra does not use an HTTP transport. > Security vulnerability CVE-2020-7238 for Netty > --- > > Key: CASSANDRA-16699 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16699 > Project: Cassandra > Issue Type: Bug >Reporter: Ethern Su >Priority: Normal > > *Cassandra Version: 3.11.10* > *Description :* > *Severity:* NVD CVSS:3.1 7.5 High > *Affecting Package*: netty-all 4.0.44.Final > *Source:* National Vulnerability Database > *Explanation from NVD:* Netty 4.1.43.Final allows HTTP Request Smuggling > because it mishandles Transfer-Encoding whitespace (such as a > [space]Transfer-Encoding:chunked line) and a later Content-Length header. > This issue exists because of an incomplete fix for CVE-2019-16869. > *Recommendation:* Upgrade package io.netty#netty-all to version 4.1.44.Final > or above. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16694) Unable to set TTL for existing cassandra cluster 3.11.5/8
[ https://issues.apache.org/jira/browse/CASSANDRA-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-16694: - Resolution: Invalid Status: Resolved (was: Open) > Unable to set TTL for existing cassandra cluster 3.11.5/8 > - > > Key: CASSANDRA-16694 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16694 > Project: Cassandra > Issue Type: Bug >Reporter: Srinivas P >Priority: Normal > > We are unable to set TTL for system_distributed keyspace and getting > following error. > Version 3.11.5/8 > cassandra@cqlsh> ALTER TABLE system_distributed.repair_history WITH > default_time_to_live = 604800; > *Unauthorized: Error from server: code=2100 [Unauthorized] message="Cannot > ALTER "* > > tried with Cassandra and cassandraops user with no luck. > Any suggestions/fixes? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16694) Unable to set TTL for existing cassandra cluster 3.11.5/8
[ https://issues.apache.org/jira/browse/CASSANDRA-16694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351846#comment-17351846 ] Brandon Williams commented on CASSANDRA-16694: -- That is only for 4.0, so you won't be able to do it in 3.x. Requesting a backport may not be unreasonable. > Unable to set TTL for existing cassandra cluster 3.11.5/8 > - > > Key: CASSANDRA-16694 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16694 > Project: Cassandra > Issue Type: Bug >Reporter: Srinivas P >Priority: Normal > > We are unable to set TTL for system_distributed keyspace and getting > following error. > Version 3.11.5/8 > cassandra@cqlsh> ALTER TABLE system_distributed.repair_history WITH > default_time_to_live = 604800; > *Unauthorized: Error from server: code=2100 [Unauthorized] message="Cannot > ALTER "* > > tried with Cassandra and cassandraops user with no luck. > Any suggestions/fixes? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16687) Support upgrade tests in CircleCI multiplexer
[
https://issues.apache.org/jira/browse/CASSANDRA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16687:
Status: Ready to Commit (was: Review In Progress)
> Support upgrade tests in CircleCI multiplexer
> -
>
> Key: CASSANDRA-16687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16687
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The CircleCI jobs for running a test repeatedly added by CASSANDRA-16625
> don't support upgrade tests. In the case of Python upgrade dtests we only
> need the {{--execute-upgrade-tests}} when calling {{pytest}}. For Java
> upgrade tests we need to build the dtest jars before running the repeated
> tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16687) Support upgrade tests in CircleCI multiplexer
[
https://issues.apache.org/jira/browse/CASSANDRA-16687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351811#comment-17351811
]
Ekaterina Dimitrova commented on CASSANDRA-16687:
-
Thank you [~adelapena].
I agree with everything said. I also see after the new run the enumeration in
the artifacts.
+1, thank you
> Support upgrade tests in CircleCI multiplexer
> -
>
> Key: CASSANDRA-16687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16687
> Project: Cassandra
> Issue Type: Task
> Components: CI
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The CircleCI jobs for running a test repeatedly added by CASSANDRA-16625
> don't support upgrade tests. In the case of Python upgrade dtests we only
> need the {{--execute-upgrade-tests}} when calling {{pytest}}. For Java
> upgrade tests we need to build the dtest jars before running the repeated
> tests.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16670) Flaky ViewComplexTest and InsertUpdateIfConditionTest
[ https://issues.apache.org/jira/browse/CASSANDRA-16670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17351796#comment-17351796 ] Ekaterina Dimitrova commented on CASSANDRA-16670: - As soon as you did the timing calculation and we have green CI, I think this is ready for commit. Thank you > Flaky ViewComplexTest and InsertUpdateIfConditionTest > - > > Key: CASSANDRA-16670 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16670 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Berenguer Blasi >Assignee: Berenguer Blasi >Priority: Normal > Fix For: 4.0-rc2, 4.0, 4.x > > > *ViewComplexTest* > Flaky > [test|https://ci-cassandra.apache.org/job/Cassandra-4.0/43/testReport/junit/org.apache.cassandra.cql3/ViewComplexTest/testPartialDeleteSelectedColumnWithoutFlush_3_/] > *InsertUpdateIfConditionTest* (CASSANDRA-16676) > Fails > [here|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/testListItem_2__clusterMinVersion_4_0_0_rc2_SNAPSHOT_/] > with a timeout. We can see in the history it takes quite a while in > [CI|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/history/] > _but_ it takes just 1m locally. Probably due to constrained resources. > Looking at the > [individual|https://ci-cassandra.apache.org/job/Cassandra-4.0/46/testReport/junit/org.apache.cassandra.cql3.validation.operations/InsertUpdateIfConditionTest/] > test cases, for compression i.e., we can see 378 at an average of 1s each it > can easily go over the timeout of 240s. Recommendation is to either move to > 'long' section of to raise the timeout for the class for CI. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
