[jira] [Commented] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770297#comment-17770297 ] Thomas Steinmaurer commented on CASSANDRA-18891: Sounds great! > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16895) Build with Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16895:
Description:
This ticket is intended to group all issues found to support Java 17 in the
future.
Upgrade steps:
* [Dependencies
|https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
be updated (not all but at least those that require an update in order to work
with Java 17)
* More encapsulated JDK internal APIs. Some of the issues might be solved with
the dependencies updates
* Currently trunk compiles if we remove the Nashorn dependency (ant script
tag, used for the test environment; UDFs) . The oracle recommendation to use
Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
we will opt in for graal-sdk licensed under UPL
* All tests to be cleaned
* CI environment to be setup
*NOTE:* GC tuning, performance testing were never agreed to be part of this
ticket.
Below is a snapshot of current CI failures with JDK17, it will be updated on a
regular basis with a date of update
*July 15th 2023*
|| ||Failing Test Classes||Ticket Numbers||
| |_Python DTests_| |
|1|-test_sjk-|CASSANDRA-18343|
| |_Java Ditributed Tests_| |
|1-6|-org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest - all
tests,-
-org.apache.cassandra.distributed.test.PrepareBatchStatementsTest - all tests,-
-org.apache.cassandra.distributed.test.IPMembershipTest - both tests,-
-org.apache.cassandra.distributed.test.MixedModeFuzzTest,-
-org.apache.cassandra.distributed.test.ReprepareFuzzTest,-
-org.apache.cassandra.distributed.test.ReprepareNewBehaviourTest-|CASSANDRA-16304|
|7,8|-org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
- all tests-
-org.apache.cassandra.distributed.test.InternodeEncryptionOptionsTest - all
tests-|Both tests suffer from CASSANDRA-18180 -
*ready to commit; blocked on being ready to drop JDK8*
fwiw, using the CASSANDRA-18180 branch, only the
negotiatedProtocolMustBeAcceptedProtocolTest fails in both these tests.
EDIT: We will need a ticket for this one post CASSANDRA-18180. TLSv1.1 failed
to negotiate (netty complains about certificate_unknown). Changes in JDK17
config to be checked - done
EDIT2: CASSANDRA-18540|
|-9-|-org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest
- 2 tests-|CASSANDRA-18180 ready to commit; blocked on being ready to drop JDK8|
| |_Unit Tests_| |
|1|-org.apache.cassandra.repair.RepairJobTest - 1 test-|CASSANDRA-18329|
|2|-org.apache.cassandra.security.SSLFactoryTest - all tests-|CASSANDRA-17992|
|3,4|-org.apache.cassandra.db.memtable.MemtableSizeOffheapBuffersTest,-
-org.apache.cassandra.utils.concurrent.RefCountedTest-|CASSANDRA-18329|
|5,6|-org.apache.cassandra.cql3.validation.entities.UFJavaTest,-
-org.apache.cassandra.cql3.validation.entities.UFSecurityTest-|CASSANDRA-18190;
ready to commit; blocked on being ready to drop JDK8|
|7|-org.apache.cassandra.cql3.EmptyValuesTest-|CASSANDRA-18436|
|8|{-}org.apache.cassandra.transport.MessagePayloadTest{-}.jdk17-|CASSANDRA-18437|
|9|-StandaloneSplitterWithCQLTesterTest/testSplittingMultipleSSTables-|CASSANDRA-18685|
| |_Burn tests_| |
|1|-org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression-|CASSANDRA-18570|
was:
This ticket is intended to group all issues found to support Java 17 in the
future.
Upgrade steps:
* [Dependencies
|https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
be updated (not all but at least those that require an update in order to work
with Java 17)
* More encapsulated JDK internal APIs. Some of the issues might be solved with
the dependencies updates
* Currently trunk compiles if we remove the Nashorn dependency (ant script
tag, used for the test environment; UDFs) . The oracle recommendation to use
Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
we will opt in for graal-sdk licensed under UPL
* All tests to be cleaned
* CI environment to be setup
*NOTE:* GC tuning, performance testing were never agreed to be part of this
ticket.
Below is a snapshot of current CI failures with JDK17, it will be updated on a
regular basis with a date of update
*July 15th 2023*
|| ||Failing Test Classes||Ticket Numbers||
| |_Python DTests_| |
|1|-test_sjk-|CASSANDRA-18343|
| |_Java Ditributed Tests_| |
|1-6|-org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest - all
tests,-
-org.apache.cassandra.distributed.test.PrepareBatchStatementsTest - all tests,-
-org.apache.cassandra.distributed.test.IPMembershipTest - both tests,-
-org.apache.cassandra.distributed.test.MixedModeFuzzTest,-
-org.apache.cassandra.distributed.test.ReprepareFuzzTest,-
-org.apache.cassandra.distributed.test.ReprepareNewBehaviourTest-|CASSANDRA-16304|
[jira] [Updated] (CASSANDRA-16895) Build with Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ekaterina Dimitrova updated CASSANDRA-16895:
Description:
This ticket is intended to group all issues found to support Java 17 in the
future.
Upgrade steps:
* [Dependencies
|https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
be updated (not all but at least those that require an update in order to work
with Java 17)
* More encapsulated JDK internal APIs. Some of the issues might be solved with
the dependencies updates
* Currently trunk compiles if we remove the Nashorn dependency (ant script
tag, used for the test environment; UDFs) . The oracle recommendation to use
Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
we will opt in for graal-sdk licensed under UPL
* All tests to be cleaned
* CI environment to be setup
*NOTE:* GC tuning, performance testing were never agreed to be part of this
ticket.
Below is a snapshot of current CI failures with JDK17, it will be updated on a
regular basis with a date of update
*July 15th 2023*
|| ||Failing Test Classes||Ticket Numbers||
| |_Python DTests_| |
|1|-test_sjk-|CASSANDRA-18343|
| |_Java Ditributed Tests_| |
|1-6|-org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest - all
tests,-
-org.apache.cassandra.distributed.test.PrepareBatchStatementsTest - all tests,-
-org.apache.cassandra.distributed.test.IPMembershipTest - both tests,-
-org.apache.cassandra.distributed.test.MixedModeFuzzTest,-
-org.apache.cassandra.distributed.test.ReprepareFuzzTest,-
-org.apache.cassandra.distributed.test.ReprepareNewBehaviourTest-|CASSANDRA-16304|
|7,8|-org.apache.cassandra.distributed.test.NativeTransportEncryptionOptionsTest
- all tests-
-org.apache.cassandra.distributed.test.InternodeEncryptionOptionsTest - all
tests-|Both tests suffer from CASSANDRA-18180 -
*ready to commit; blocked on being ready to drop JDK8*
fwiw, using the CASSANDRA-18180 branch, only the
negotiatedProtocolMustBeAcceptedProtocolTest fails in both these tests.
EDIT: We will need a ticket for this one post CASSANDRA-18180. TLSv1.1 failed
to negotiate (netty complains about certificate_unknown). Changes in JDK17
config to be checked - done
EDIT2: CASSANDRA-18540|
|-9-|-org.apache.cassandra.distributed.test.SSTableLoaderEncryptionOptionsTest
- 2 tests-|CASSANDRA-18180 ready to commit; blocked on being ready to drop JDK8|
| |_Unit Tests_| |
|1|-org.apache.cassandra.repair.RepairJobTest - 1 test-|CASSANDRA-17884|
|2|org.apache.cassandra.security.SSLFactoryTest - all tests|CASSANDRA-17992|
|3,4|-org.apache.cassandra.db.memtable.MemtableSizeOffheapBuffersTest,-
-org.apache.cassandra.utils.concurrent.RefCountedTest-|CASSANDRA-18329|
|5,6|-org.apache.cassandra.cql3.validation.entities.UFJavaTest,-
-org.apache.cassandra.cql3.validation.entities.UFSecurityTest-|CASSANDRA-18190;
ready to commit; blocked on being ready to drop JDK8|
|7|-org.apache.cassandra.cql3.EmptyValuesTest-|CASSANDRA-18436|
|8|{-}org.apache.cassandra.transport.MessagePayloadTest{-}.jdk17-|CASSANDRA-18437|
|9|-StandaloneSplitterWithCQLTesterTest/testSplittingMultipleSSTables-|CASSANDRA-18685|
| |_Burn tests_| |
|1|-org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression-|CASSANDRA-18570|
was:
This ticket is intended to group all issues found to support Java 17 in the
future.
Upgrade steps:
* [Dependencies
|https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
be updated (not all but at least those that require an update in order to work
with Java 17)
* More encapsulated JDK internal APIs. Some of the issues might be solved with
the dependencies updates
* Currently trunk compiles if we remove the Nashorn dependency (ant script
tag, used for the test environment; UDFs) . The oracle recommendation to use
Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
we will opt in for graal-sdk licensed under UPL
* All tests to be cleaned
* CI environment to be setup
*NOTE:* GC tuning, performance testing were never agreed to be part of this
ticket.
Below is a snapshot of current CI failures with JDK17, it will be updated on a
regular basis with a date of update
*July 15th 2023*
|| ||Failing Test Classes||Ticket Numbers||
| |_Python DTests_| |
|1|-test_sjk-|CASSANDRA-18343|
| |_Java Ditributed Tests_| |
|1-6|-org.apache.cassandra.distributed.test.ReprepareOldBehaviourTest - all
tests,-
-org.apache.cassandra.distributed.test.PrepareBatchStatementsTest - all tests,-
-org.apache.cassandra.distributed.test.IPMembershipTest - both tests,-
-org.apache.cassandra.distributed.test.MixedModeFuzzTest, -
-org.apache.cassandra.distributed.test.ReprepareFuzzTest,-
-org.apache.cassandra.distributed.test.ReprepareNewBehaviourTest-|CASSANDRA-16304|
[jira] [Updated] (CASSANDRA-18893) Upgrade hdrhistogram
[ https://issues.apache.org/jira/browse/CASSANDRA-18893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18893: Epic Link: CASSANDRA-16895 > Upgrade hdrhistogram > > > Key: CASSANDRA-18893 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18893 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > We are on 2.1.9, but some breaking changes for J9+ were introduced only in > 2.1.10 (we don't hit them in our CI but a user reported they saw NoClassFound > in some testing) > https://github.com/HdrHistogram/HdrHistogram/commit/c410c5c2699b69ce0eb026ff954fefc4045ec363 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18805) Upgrade caffeine to 3.1.8
[ https://issues.apache.org/jira/browse/CASSANDRA-18805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770265#comment-17770265 ] Ekaterina Dimitrova commented on CASSANDRA-18805: - I just rebased the branch and incorporated the solution for the flakiness suggested by Shailaja Koppu, plus tiny feedback by [~jlewandowski]. This run shows that the flaky test is fixed: https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2524/workflows/7f55e5a0-2a46-43e6-94aa-d24acf79fa2b If everyone is happy, I will propagate the final patch to trunk, run full CI on both 5.0 and trunk, and move with a commit. > Upgrade caffeine to 3.1.8 > - > > Key: CASSANDRA-18805 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18805 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > 3.1.8 is based on Java 11. This version is testing with newer JDK versions, > while 2.x versions are based on JDK8, and as I understand, only bug-fix > releases are expected. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18893) Upgrade hdrhistogram
[ https://issues.apache.org/jira/browse/CASSANDRA-18893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770250#comment-17770250 ] Ekaterina Dimitrova commented on CASSANDRA-18893: - I am wondering whether to update it also on 4.0+... But at least we should do it for 5.0+. I suggest we upgrade to 2.1.12. I do not see any breaking changes for us from the commits. I have not found the release notes doc so far; I will search again tomorrow. In the meantime, I am starting a CI run on 5.0 branch here: https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra?branch=18893-5.0 > Upgrade hdrhistogram > > > Key: CASSANDRA-18893 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18893 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > We are on 2.1.9, but some breaking changes for J9+ were introduced only in > 2.1.10 (we don't hit them in our CI but a user reported they saw NoClassFound > in some testing) > https://github.com/HdrHistogram/HdrHistogram/commit/c410c5c2699b69ce0eb026ff954fefc4045ec363 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18893) Upgrade hdrhistogram
[ https://issues.apache.org/jira/browse/CASSANDRA-18893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18893: Change Category: Operability Complexity: Normal Component/s: Dependencies Assignee: Ekaterina Dimitrova Status: Open (was: Triage Needed) > Upgrade hdrhistogram > > > Key: CASSANDRA-18893 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18893 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > We are on 2.1.9, but some breaking changes for J9+ were introduced only in > 2.1.10 (we don't hit them in our CI but a user reported they saw NoClassFound > in some testing) > https://github.com/HdrHistogram/HdrHistogram/commit/c410c5c2699b69ce0eb026ff954fefc4045ec363 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18893) Upgrade hdrhistogram
[ https://issues.apache.org/jira/browse/CASSANDRA-18893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ekaterina Dimitrova updated CASSANDRA-18893: Fix Version/s: 5.0.x 5.x > Upgrade hdrhistogram > > > Key: CASSANDRA-18893 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18893 > Project: Cassandra > Issue Type: Task > Components: Dependencies >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.0.x, 5.x > > > We are on 2.1.9, but some breaking changes for J9+ were introduced only in > 2.1.10 (we don't hit them in our CI but a user reported they saw NoClassFound > in some testing) > https://github.com/HdrHistogram/HdrHistogram/commit/c410c5c2699b69ce0eb026ff954fefc4045ec363 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18893) Upgrade hdrhistogram
Ekaterina Dimitrova created CASSANDRA-18893: --- Summary: Upgrade hdrhistogram Key: CASSANDRA-18893 URL: https://issues.apache.org/jira/browse/CASSANDRA-18893 Project: Cassandra Issue Type: Task Reporter: Ekaterina Dimitrova We are on 2.1.9, but some breaking changes for J9+ were introduced only in 2.1.10 (we don't hit them in our CI but a user reported they saw NoClassFound in some testing) https://github.com/HdrHistogram/HdrHistogram/commit/c410c5c2699b69ce0eb026ff954fefc4045ec363 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16999) system.peers and system.peers_v2 do not contain the native_transport and/or native_transport_port_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770211#comment-17770211 ] Bret McGuire commented on CASSANDRA-16999: -- Hey all, apologies for the delay on my end. I'll try to take a look at this over the weekend or early next week! > system.peers and system.peers_v2 do not contain the native_transport and/or > native_transport_port_ssl > - > > Key: CASSANDRA-16999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16999 > Project: Cassandra > Issue Type: Bug > Components: Local/Other >Reporter: Steve Lacerda >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > > system.peers_v2 includes a “native_port” but has no notion of > native_transport_port vs. native_transport_port_ssl. Given this limited > information, there’s no clear way for the driver to know that different ports > are being used for SSL vs. non-SSL or which of those two ports is identified > by “native_port”. > > The issue we ran into is that the java driver, since it has no notion of the > transport port SSL, the driver was only using the contact points and was not > load balancing. > > The customer had both set: > native_transport_port: 9042 > native_transport_port_ssl: 9142 > > They were attempting to connect to 9142, but that was failing. They could > only use 9042, and so their applications load balancing was failing. We found > that any node that was a contact point was connecting, but the other nodes > were never acting as coordinators. > > There are still issues in the driver, for which I have created JAVA-2967, > which also refers to JAVA-2638, but the system.peers and system.peers_v2 > tables should both contain native_transport_port and > native_transport_port_ssl. > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-17686) Test failure: repair_tests/preview_repair_test.py::TestPreviewRepair::test_preview
[
https://issues.apache.org/jira/browse/CASSANDRA-17686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-17686:
-
Fix Version/s: 4.1.x
> Test failure:
> repair_tests/preview_repair_test.py::TestPreviewRepair::test_preview
> --
>
> Key: CASSANDRA-17686
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17686
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Priority: Normal
> Fix For: 4.1.x, 5.x
>
>
> The Python dtest
> {{repair_tests/preview_repair_test.py::TestPreviewRepair::test_preview}} is
> flaky at least in {{trunk}}, with a flakiness < 1%.
> I haven't seen the failure on Jenkins but on [this CircleCI
> run|https://app.circleci.com/pipelines/github/adelapena/cassandra/1662/workflows/b5753cdb-2d08-44d0-9caf-79b5fd0b01f4]
> for CASSANDRA-17458.
> The failure can also be [reproduced in the
> multiplexer|https://app.circleci.com/pipelines/github/adelapena/cassandra/1667/workflows/60ba0ade-7e4e-4728-a7ff-3872f2a1903c],
> with 7 failures in 5000 iterations:
> {code}
> test teardown failure
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node3] 'ERROR [CompactionExecutor:3] 2022-06-06 10:58:08,720
> JVMStabilityInspector.java:68 - Exception in thread
> Thread[CompactionExecutor:3,5,CompactionExecutor]\njava.util.ConcurrentModificationException:
> null\n\tat java.util.HashMap$HashIterator.nextNode(HashMap.java:1469)\n\tat
> java.util.HashMap$KeyIterator.next(HashMap.java:1493)\n\tat
> java.util.AbstractCollection.toArray(AbstractCollection.java:141)\n\tat
> com.google.common.collect.ImmutableSet.copyOf(ImmutableSet.java:211)\n\tat
> org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy.getSSTables(SizeTieredCompactionStrategy.java:341)\n\tat
>
> org.apache.cassandra.db.compaction.PendingRepairManager.getRepairFinishedCompactionTask(PendingRepairManager.java:271)\n\tat
>
> org.apache.cassandra.db.compaction.PendingRepairManager.getNextRepairFinishedTask(PendingRepairManager.java:359)\n\tat
>
> org.apache.cassandra.db.compaction.AbstractStrategyHolder$TaskSupplier.getTask(AbstractStrategyHolder.java:65)\n\tat
>
> org.apache.cassandra.db.compaction.PendingRepairHolder.getNextRepairFinishedTask(PendingRepairHolder.java:159)\n\tat
>
> org.apache.cassandra.db.compaction.CompactionStrategyManager.getNextBackgroundTask(CompactionStrategyManager.java:200)\n\tat
>
> org.apache.cassandra.db.compaction.CompactionManager$BackgroundCompactionCandidate.run(CompactionManager.java:291)\n\tat
> org.apache.cassandra.concurrent.FutureTask$2.call(FutureTask.java:98)\n\tat
> org.apache.cassandra.concurrent.FutureTask.call(FutureTask.java:47)\n\tat
> org.apache.cassandra.concurrent.FutureTask.run(FutureTask.java:57)\n\tat
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)\n\tat
>
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.lang.Thread.run(Thread.java:748)']
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770191#comment-17770191
]
David Capwell commented on CASSANDRA-18890:
---
I know the fix for this, but wanted to first make sure I can repo. I fixed my
script to work with jdk17 and _repeat jobs again; running here
https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=deleteme
> Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
> -
>
> Key: CASSANDRA-18890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: David Capwell
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
> is flaky in both 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
> {code}
> junit.framework.AssertionFailedError: Property error detected:
> Seed = 3695691971125975155
> Examples = 2
> Pure = false
> Error: property test did not complete within PT1M
> Values:
> at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
> at accord.utils.Property$SingleBuilder.check(Property.java:223)
> at accord.utils.Property$ForBuilder.check(Property.java:124)
> at
> org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is around 6%. The CircleCI runs above have been generated with:
> {code}
> .circleci/generate.sh -p -s \
> -e
> REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
> -e REPEATED_UTESTS_COUNT=500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRASC-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRASC-73: - Fix Version/s: 1.0 Source Control Link: https://github.com/apache/cassandra-sidecar/commit/0dd7a14f7e70dc8a40d20eba5c78dc4f6a580e17 Resolution: Fixed Status: Resolved (was: Ready to Commit) > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > Fix For: 1.0 > > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770190#comment-17770190 ] ASF subversion and git services commented on CASSANDRASC-73: Commit 0dd7a14f7e70dc8a40d20eba5c78dc4f6a580e17 in cassandra-sidecar's branch refs/heads/trunk from Arjun Ashok [ https://gitbox.apache.org/repos/asf?p=cassandra-sidecar.git;h=0dd7a14 ] CASSANDRASC-73: Updates token-ranges endpoint to return additional instance metadata Patch by Arjun Ashok; Reviewed by Dinesh Joshi, Francisco Guerrero, Yifan Cai for CASSANDRASC-73 > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-sidecar] branch trunk updated: CASSANDRASC-73: Updates token-ranges endpoint to return additional instance metadata
This is an automated email from the ASF dual-hosted git repository.
ycai pushed a commit to branch trunk
in repository https://gitbox.apache.org/repos/asf/cassandra-sidecar.git
The following commit(s) were added to refs/heads/trunk by this push:
new 0dd7a14 CASSANDRASC-73: Updates token-ranges endpoint to return
additional instance metadata
0dd7a14 is described below
commit 0dd7a14f7e70dc8a40d20eba5c78dc4f6a580e17
Author: Arjun Ashok
AuthorDate: Mon Sep 18 16:41:07 2023 -0700
CASSANDRASC-73: Updates token-ranges endpoint to return additional instance
metadata
Patch by Arjun Ashok; Reviewed by Dinesh Joshi, Francisco Guerrero, Yifan
Cai for CASSANDRASC-73
---
CHANGES.txt| 1 +
.../adapters/base/CassandraStorageOperations.java | 12 +-
.../adapters/base/TokenRangeReplicaProvider.java | 52 +--
.../base/TokenRangeReplicaProviderTest.java| 155 -
.../sidecar/client/SidecarClientTest.java | 27 +++-
.../common/data/TokenRangeReplicasResponse.java| 119 ++--
.../tokenrange/BaseTokenRangeIntegrationTest.java | 20 ++-
7 files changed, 313 insertions(+), 73 deletions(-)
diff --git a/CHANGES.txt b/CHANGES.txt
index a465ed3..4dff0fd 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1,5 +1,6 @@
1.0.0
-
+ * Updates token-ranges endpoint to return additional instance metadata
(CASSANDRASC-73)
* Shade Jackson completely to prevent incompatibility issues (CASSANDRASC-75)
* Adds endpoint to serve read/write replica-sets by token-ranges
(CASSANDRASC-60)
* Split unit tests and integration tests in CircleCI config (CASSANDRASC-72)
diff --git
a/adapters/base/src/main/java/org/apache/cassandra/sidecar/adapters/base/CassandraStorageOperations.java
b/adapters/base/src/main/java/org/apache/cassandra/sidecar/adapters/base/CassandraStorageOperations.java
index 68769f2..efe0fa1 100644
---
a/adapters/base/src/main/java/org/apache/cassandra/sidecar/adapters/base/CassandraStorageOperations.java
+++
b/adapters/base/src/main/java/org/apache/cassandra/sidecar/adapters/base/CassandraStorageOperations.java
@@ -49,20 +49,16 @@ public class CassandraStorageOperations implements
StorageOperations
protected final TokenRangeReplicaProvider tokenRangeReplicaProvider;
/**
- * Creates a new instance with the provided {@link JmxClient}
+ * Creates a new instance with the provided {@link JmxClient} and {@link
DnsResolver}
*
* @param jmxClient the JMX client used to communicate with the Cassandra
instance
+ * @param dnsResolver the DNS resolver used to lookup replicas
*/
public CassandraStorageOperations(JmxClient jmxClient, DnsResolver
dnsResolver)
-{
-this(jmxClient, new RingProvider(jmxClient, dnsResolver));
-}
-
-public CassandraStorageOperations(JmxClient jmxClient, RingProvider
ringProvider)
{
this.jmxClient = jmxClient;
-this.ringProvider = ringProvider;
-this.tokenRangeReplicaProvider = new
TokenRangeReplicaProvider(jmxClient);
+this.ringProvider = new RingProvider(jmxClient, dnsResolver);
+this.tokenRangeReplicaProvider = new
TokenRangeReplicaProvider(jmxClient, dnsResolver);
}
/**
diff --git
a/adapters/base/src/main/java/org/apache/cassandra/sidecar/adapters/base/TokenRangeReplicaProvider.java
b/adapters/base/src/main/java/org/apache/cassandra/sidecar/adapters/base/TokenRangeReplicaProvider.java
index f8e0d39..24162f1 100644
---
a/adapters/base/src/main/java/org/apache/cassandra/sidecar/adapters/base/TokenRangeReplicaProvider.java
+++
b/adapters/base/src/main/java/org/apache/cassandra/sidecar/adapters/base/TokenRangeReplicaProvider.java
@@ -30,6 +30,7 @@ import java.util.Objects;
import java.util.function.Function;
import java.util.stream.Collectors;
+import com.google.common.net.HostAndPort;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
@@ -38,6 +39,8 @@ import org.apache.cassandra.sidecar.common.JmxClient;
import org.apache.cassandra.sidecar.common.data.GossipInfoResponse;
import org.apache.cassandra.sidecar.common.data.TokenRangeReplicasResponse;
import
org.apache.cassandra.sidecar.common.data.TokenRangeReplicasResponse.ReplicaInfo;
+import
org.apache.cassandra.sidecar.common.data.TokenRangeReplicasResponse.ReplicaMetadata;
+import org.apache.cassandra.sidecar.common.dns.DnsResolver;
import org.apache.cassandra.sidecar.common.utils.GossipInfoParser;
import org.jetbrains.annotations.NotNull;
@@ -52,17 +55,21 @@ import static
org.apache.cassandra.sidecar.adapters.base.TokenRangeReplicas.gene
*/
public class TokenRangeReplicaProvider
{
+
private interface KeyspaceToRangeMappingFunc extends Function, List>>
{
}
protected final JmxClient jmxClient;
+private final DnsResolver dnsResolver;
private static final Logger LOGGER =
LoggerFactory.getLogger(TokenRangeReplicaProvider.class);
-
[jira] [Commented] (CASSANDRA-16949) Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770188#comment-17770188
]
Sam Tunnicliffe commented on CASSANDRA-16949:
-
We may as well commit this to 4.0/4.1/5.0 as this is essentially a test-only
fix (SimpleClient is only used in tests / stress and the changes there only
really amount to additional TRACE logging anyway). WDYT?
> Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
> ---
>
> Key: CASSANDRA-16949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16949
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1037/workflows/c728d370-49b9-41aa-bdfb-8c41cf0355d8/jobs/6577/parallel-runs/3
> {code}
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> Tests run: 9, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 12.926 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> handleCorruptionOfLargeMessageFrame(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] null
> [junit-timeout] junit.framework.AssertionFailedError
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:484)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame(CQLConnectionTest.java:217)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testNegativeEnvelopeBodySize(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testNegativeEnvelopeBodySize(CQLConnectionTest.java:326)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testUnrecoverableMessageDecodingErrors(org.apache.cassandra.transport.CQLConnectionTest):
>FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
>
[jira] [Updated] (CASSANDRASC-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRASC-73: - Reviewers: Dinesh Joshi, Francisco Guerrero, Yifan Cai (was: Francisco Guerrero, Yifan Cai) > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16949) Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16949:
Status: Ready to Commit (was: Review In Progress)
+1 LGTM
> Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
> ---
>
> Key: CASSANDRA-16949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16949
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1037/workflows/c728d370-49b9-41aa-bdfb-8c41cf0355d8/jobs/6577/parallel-runs/3
> {code}
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> Tests run: 9, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 12.926 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> handleCorruptionOfLargeMessageFrame(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] null
> [junit-timeout] junit.framework.AssertionFailedError
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:484)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame(CQLConnectionTest.java:217)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testNegativeEnvelopeBodySize(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testNegativeEnvelopeBodySize(CQLConnectionTest.java:326)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testUnrecoverableMessageDecodingErrors(org.apache.cassandra.transport.CQLConnectionTest):
>FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testUnrecoverableMessageDecodingErrors(CQLConnectionTest.java:392)
> [junit-timeout]
[jira] [Updated] (CASSANDRASC-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yifan Cai updated CASSANDRASC-73: - Status: Ready to Commit (was: Review In Progress) > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18856) Test failure: rebuild_test.TestRebuild.test_resumable_rebuild
[
https://issues.apache.org/jira/browse/CASSANDRA-18856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-18856:
-
Test and Documentation Plan: run CI
Status: Patch Available (was: Open)
> Test failure: rebuild_test.TestRebuild.test_resumable_rebuild
> -
>
> Key: CASSANDRA-18856
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18856
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> https://app.circleci.com/pipelines/github/driftx/cassandra/1294/workflows/04464235-3bcf-433e-ae81-206aa2c9c874/jobs/54042/tests
> {quote}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node3] 'ERROR
> [Stream-Deserializer-/127.0.0.2:7000-d94b6b54] 2023-09-15 16:04:30,685
> CassandraEntireSSTableStreamReader.java:146 - [Stream
> 8d7c61b0-53e1-11ee-a721-a91a3065a930] Error while reading sstable from stream
> for table = ks.cf\njava.nio.channels.ClosedChannelException: null\n\tat
> org.apache.cassandra.net.AsyncStreamingInputPlus.reBuffer(AsyncStreamingInputPlus.java:119)\n\tat
>
> org.apache.cassandra.net.AsyncStreamingInputPlus.consume(AsyncStreamingInputPlus.java:139)\n\tat
>
> org.apache.cassandra.io.sstable.SSTableZeroCopyWriter.write(SSTableZeroCopyWriter.java:218)\n\tat
>
> org.apache.cassandra.io.sstable.SSTableZeroCopyWriter.writeComponent(SSTableZeroCopyWriter.java:207)\n\tat
>
> org.apache.cassandra.db.streaming.CassandraEntireSSTableStreamReader.read(CassandraEntireSSTableStreamReader.java:124)\n\tat
>
> org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:87)\n\tat
>
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:50)\n\tat
>
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:36)\n\tat
>
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:50)\n\tat
>
> org.apache.cassandra.streaming.StreamDeserializingTask.run(StreamDeserializingTask.java:59)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:833)', [node3] 'ERROR
> [Stream-Deserializer-/127.0.0.2:7000-6f7e3946] 2023-09-15 16:04:30,687
> CassandraEntireSSTableStreamReader.java:146 - [Stream
> 8d7c61b0-53e1-11ee-a721-a91a3065a930] Error while reading sstable from stream
> for table = ks.cf\njava.nio.channels.ClosedChannelException: null\n\tat
> org.apache.cassandra.net.AsyncStreamingInputPlus.reBuffer(AsyncStreamingInputPlus.java:119)\n\tat
>
> org.apache.cassandra.net.AsyncStreamingInputPlus.consume(AsyncStreamingInputPlus.java:139)\n\tat
>
> org.apache.cassandra.io.sstable.SSTableZeroCopyWriter.write(SSTableZeroCopyWriter.java:218)\n\tat
>
> org.apache.cassandra.io.sstable.SSTableZeroCopyWriter.writeComponent(SSTableZeroCopyWriter.java:207)\n\tat
>
> org.apache.cassandra.db.streaming.CassandraEntireSSTableStreamReader.read(CassandraEntireSSTableStreamReader.java:124)\n\tat
>
> org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:87)\n\tat
>
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:50)\n\tat
>
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:36)\n\tat
>
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:50)\n\tat
>
> org.apache.cassandra.streaming.StreamDeserializingTask.run(StreamDeserializingTask.java:59)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:833)']"
> {quote}
> This is probably similar to CASSANDRA-18815
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18856) Test failure: rebuild_test.TestRebuild.test_resumable_rebuild
[
https://issues.apache.org/jira/browse/CASSANDRA-18856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770181#comment-17770181
]
Brandon Williams commented on CASSANDRA-18856:
--
Well I haven't been able to reproduce the attempt to delete a nonexistent file,
but this is [passing 500 runs
here|https://app.circleci.com/pipelines/github/driftx/cassandra/1315/workflows/8377b4af-d61f-4349-8bc0-47b02af17484/jobs/56098]
and the streaming error is more common, so I suggest we get that committed and
we can open a new ticket for the nonexistent file when it occurs again.
> Test failure: rebuild_test.TestRebuild.test_resumable_rebuild
> -
>
> Key: CASSANDRA-18856
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18856
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Streaming
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> https://app.circleci.com/pipelines/github/driftx/cassandra/1294/workflows/04464235-3bcf-433e-ae81-206aa2c9c874/jobs/54042/tests
> {quote}
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node3] 'ERROR
> [Stream-Deserializer-/127.0.0.2:7000-d94b6b54] 2023-09-15 16:04:30,685
> CassandraEntireSSTableStreamReader.java:146 - [Stream
> 8d7c61b0-53e1-11ee-a721-a91a3065a930] Error while reading sstable from stream
> for table = ks.cf\njava.nio.channels.ClosedChannelException: null\n\tat
> org.apache.cassandra.net.AsyncStreamingInputPlus.reBuffer(AsyncStreamingInputPlus.java:119)\n\tat
>
> org.apache.cassandra.net.AsyncStreamingInputPlus.consume(AsyncStreamingInputPlus.java:139)\n\tat
>
> org.apache.cassandra.io.sstable.SSTableZeroCopyWriter.write(SSTableZeroCopyWriter.java:218)\n\tat
>
> org.apache.cassandra.io.sstable.SSTableZeroCopyWriter.writeComponent(SSTableZeroCopyWriter.java:207)\n\tat
>
> org.apache.cassandra.db.streaming.CassandraEntireSSTableStreamReader.read(CassandraEntireSSTableStreamReader.java:124)\n\tat
>
> org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:87)\n\tat
>
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:50)\n\tat
>
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:36)\n\tat
>
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:50)\n\tat
>
> org.apache.cassandra.streaming.StreamDeserializingTask.run(StreamDeserializingTask.java:59)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:833)', [node3] 'ERROR
> [Stream-Deserializer-/127.0.0.2:7000-6f7e3946] 2023-09-15 16:04:30,687
> CassandraEntireSSTableStreamReader.java:146 - [Stream
> 8d7c61b0-53e1-11ee-a721-a91a3065a930] Error while reading sstable from stream
> for table = ks.cf\njava.nio.channels.ClosedChannelException: null\n\tat
> org.apache.cassandra.net.AsyncStreamingInputPlus.reBuffer(AsyncStreamingInputPlus.java:119)\n\tat
>
> org.apache.cassandra.net.AsyncStreamingInputPlus.consume(AsyncStreamingInputPlus.java:139)\n\tat
>
> org.apache.cassandra.io.sstable.SSTableZeroCopyWriter.write(SSTableZeroCopyWriter.java:218)\n\tat
>
> org.apache.cassandra.io.sstable.SSTableZeroCopyWriter.writeComponent(SSTableZeroCopyWriter.java:207)\n\tat
>
> org.apache.cassandra.db.streaming.CassandraEntireSSTableStreamReader.read(CassandraEntireSSTableStreamReader.java:124)\n\tat
>
> org.apache.cassandra.db.streaming.CassandraIncomingFile.read(CassandraIncomingFile.java:87)\n\tat
>
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:50)\n\tat
>
> org.apache.cassandra.streaming.messages.IncomingStreamMessage$1.deserialize(IncomingStreamMessage.java:36)\n\tat
>
> org.apache.cassandra.streaming.messages.StreamMessage.deserialize(StreamMessage.java:50)\n\tat
>
> org.apache.cassandra.streaming.StreamDeserializingTask.run(StreamDeserializingTask.java:59)\n\tat
>
> io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)\n\tat
> java.base/java.lang.Thread.run(Thread.java:833)']"
> {quote}
> This is probably similar to CASSANDRA-18815
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18816) Add support for repair coordinator to retry messages that timeout
[ https://issues.apache.org/jira/browse/CASSANDRA-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770164#comment-17770164 ] Andres de la Peña commented on CASSANDRA-18816: --- So anyone using that script has not been running repeated tests before commit since jdk17 was added? > Add support for repair coordinator to retry messages that timeout > - > > Key: CASSANDRA-18816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18816 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Repair >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.0-alpha2 > > Time Spent: 13h 10m > Remaining Estimate: 0h > > Now that CASSANDRA-15399 is in, most of the repair messages have a state that > they can check against to make message delivery idempotent, allowing the > coordinator to retry such messages; a few of the most critical messages to > retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and > SYNC_RSP. > With this I propose making the coordinator able to retry these key messages > to try and make repair more resilient to ephemeral issues. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770074#comment-17770074
]
Jacek Lewandowski edited comment on CASSANDRA-18361 at 9/28/23 4:41 PM:
4.0 probably suffers from the same problem
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/954/workflows/e1412dad-20e6-4fbc-a517-f18d984aa461
https://github.com/apache/cassandra/pull/2751
was (Author: jlewandowski):
4.0 probably suffers from the same problem
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18816) Add support for repair coordinator to retry messages that timeout
[ https://issues.apache.org/jira/browse/CASSANDRA-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770157#comment-17770157 ] David Capwell commented on CASSANDRA-18816: --- my script to setup CI broke when jdk17 was added, bug in my script. Fixed locally and see that the _repeat jobs are added back > Add support for repair coordinator to retry messages that timeout > - > > Key: CASSANDRA-18816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18816 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Repair >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.0-alpha2 > > Time Spent: 13h 10m > Remaining Estimate: 0h > > Now that CASSANDRA-15399 is in, most of the repair messages have a state that > they can check against to make message delivery idempotent, allowing the > coordinator to retry such messages; a few of the most critical messages to > retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and > SYNC_RSP. > With this I propose making the coordinator able to retry these key messages > to try and make repair more resilient to ephemeral issues. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18217) Allow CQL queries on multiple indexes without ALLOW FILTERING
[ https://issues.apache.org/jira/browse/CASSANDRA-18217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Caleb Rackliffe updated CASSANDRA-18217: Fix Version/s: 5.0 (was: NA) > Allow CQL queries on multiple indexes without ALLOW FILTERING > - > > Key: CASSANDRA-18217 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18217 > Project: Cassandra > Issue Type: Improvement > Components: Feature/SAI >Reporter: Mike Adamson >Assignee: Andres de la Peña >Priority: Normal > Labels: SAI > Fix For: 5.0 > > > The Index Group index was added by > [CASSANDRA-16092|https://issues.apache.org/jira/browse/CASSANDRA-16092] to > allow indexes to be grouped and have more than one index expression in a > query. This did not make any changes to StatementRestrictions so CQL queries > using multiple index expression still need to add ALLOW FILTERING to the > query to be valid. > This restriction should be removed such that any number of index expressions > can be used on a CQL query without needing ALLOW FILTERING. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-17092) CEP-15: Accord Beta
[ https://issues.apache.org/jira/browse/CASSANDRA-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770154#comment-17770154 ] Jacek Lewandowski commented on CASSANDRA-17092: --- [~maedhroz] that is great news, thanks > CEP-15: Accord Beta > --- > > Key: CASSANDRA-17092 > URL: https://issues.apache.org/jira/browse/CASSANDRA-17092 > Project: Cassandra > Issue Type: Epic > Components: Accord >Reporter: Benedict Elliott Smith >Assignee: Benedict Elliott Smith >Priority: Normal > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18816) Add support for repair coordinator to retry messages that timeout
[ https://issues.apache.org/jira/browse/CASSANDRA-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770153#comment-17770153 ] David Capwell commented on CASSANDRA-18816: --- bq. I don't see any repeated runs on the CI results above, were they run? Looks like not. I use my own script for setting up CI and looks like it didn't add repeat jobs... it was before jdk8, so the recent changes must not be working with my script... will try to figure out what's going on > Add support for repair coordinator to retry messages that timeout > - > > Key: CASSANDRA-18816 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18816 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Repair >Reporter: David Capwell >Assignee: David Capwell >Priority: Normal > Fix For: 5.0-alpha2 > > Time Spent: 13h 10m > Remaining Estimate: 0h > > Now that CASSANDRA-15399 is in, most of the repair messages have a state that > they can check against to make message delivery idempotent, allowing the > coordinator to retry such messages; a few of the most critical messages to > retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and > SYNC_RSP. > With this I propose making the coordinator able to retry these key messages > to try and make repair more resilient to ephemeral issues. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770150#comment-17770150
]
David Capwell commented on CASSANDRA-18890:
---
ok, looks like repeat tests were not run... my script for CI probably broke
when we dropped jdk8... ill look into this
> Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
> -
>
> Key: CASSANDRA-18890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: David Capwell
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
> is flaky in both 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
> {code}
> junit.framework.AssertionFailedError: Property error detected:
> Seed = 3695691971125975155
> Examples = 2
> Pure = false
> Error: property test did not complete within PT1M
> Values:
> at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
> at accord.utils.Property$SingleBuilder.check(Property.java:223)
> at accord.utils.Property$ForBuilder.check(Property.java:124)
> at
> org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is around 6%. The CircleCI runs above have been generated with:
> {code}
> .circleci/generate.sh -p -s \
> -e
> REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
> -e REPEATED_UTESTS_COUNT=500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770149#comment-17770149
]
David Capwell commented on CASSANDRA-18890:
---
bq. property test did not complete within PT1M
this is just a timeout issue, the same seed passes but looks like it just took
too long in CI. Ill bump the timeout and run again...
Thought we ran repeat tests before merging, will look into that
> Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
> -
>
> Key: CASSANDRA-18890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: David Capwell
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
> is flaky in both 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
> {code}
> junit.framework.AssertionFailedError: Property error detected:
> Seed = 3695691971125975155
> Examples = 2
> Pure = false
> Error: property test did not complete within PT1M
> Values:
> at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
> at accord.utils.Property$SingleBuilder.check(Property.java:223)
> at accord.utils.Property$ForBuilder.check(Property.java:124)
> at
> org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is around 6%. The CircleCI runs above have been generated with:
> {code}
> .circleci/generate.sh -p -s \
> -e
> REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
> -e REPEATED_UTESTS_COUNT=500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-18890:
--
Complexity: Normal
Discovered By: Unit Test
Fix Version/s: 5.x
Severity: Normal
Status: Open (was: Triage Needed)
> Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
> -
>
> Key: CASSANDRA-18890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: David Capwell
>Priority: Normal
> Fix For: 5.x
>
>
> The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
> is flaky in both 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
> {code}
> junit.framework.AssertionFailedError: Property error detected:
> Seed = 3695691971125975155
> Examples = 2
> Pure = false
> Error: property test did not complete within PT1M
> Values:
> at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
> at accord.utils.Property$SingleBuilder.check(Property.java:223)
> at accord.utils.Property$ForBuilder.check(Property.java:124)
> at
> org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is around 6%. The CircleCI runs above have been generated with:
> {code}
> .circleci/generate.sh -p -s \
> -e
> REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
> -e REPEATED_UTESTS_COUNT=500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell reassigned CASSANDRA-18890:
-
Assignee: David Capwell
> Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
> -
>
> Key: CASSANDRA-18890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Assignee: David Capwell
>Priority: Normal
>
> The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
> is flaky in both 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
> {code}
> junit.framework.AssertionFailedError: Property error detected:
> Seed = 3695691971125975155
> Examples = 2
> Pure = false
> Error: property test did not complete within PT1M
> Values:
> at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
> at accord.utils.Property$SingleBuilder.check(Property.java:223)
> at accord.utils.Property$ForBuilder.check(Property.java:124)
> at
> org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is around 6%. The CircleCI runs above have been generated with:
> {code}
> .circleci/generate.sh -p -s \
> -e
> REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
> -e REPEATED_UTESTS_COUNT=500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770146#comment-17770146
]
David Capwell commented on CASSANDRA-18890:
---
looking into it
> Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
> -
>
> Key: CASSANDRA-18890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
>
> The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
> is flaky in both 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
> {code}
> junit.framework.AssertionFailedError: Property error detected:
> Seed = 3695691971125975155
> Examples = 2
> Pure = false
> Error: property test did not complete within PT1M
> Values:
> at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
> at accord.utils.Property$SingleBuilder.check(Property.java:223)
> at accord.utils.Property$ForBuilder.check(Property.java:124)
> at
> org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is around 6%. The CircleCI runs above have been generated with:
> {code}
> .circleci/generate.sh -p -s \
> -e
> REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
> -e REPEATED_UTESTS_COUNT=500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18892) Distributed tests can return ordering columns that have not been selected
[
https://issues.apache.org/jira/browse/CASSANDRA-18892?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Adamson updated CASSANDRA-18892:
-
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990)
Complexity: Low Hanging Fruit
Discovered By: DTest
Severity: Low
Status: Open (was: Triage Needed)
> Distributed tests can return ordering columns that have not been selected
> -
>
> Key: CASSANDRA-18892
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18892
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/java
>Reporter: Mike Adamson
>Assignee: Mike Adamson
>Priority: Normal
>
> The following test fails
> {code:java}
> @Test
> public void incorrectClusteringColumnTest() throws IOException
> {
> try (Cluster cluster = init(Cluster.build(1).start()))
> {
> cluster.schemaChange(withKeyspace("CREATE TABLE %s.t (k int, c int, v
> int, primary key(k, c))"));
> cluster.coordinator(1).execute(withKeyspace("INSERT INTO %s.t (k, c,
> v) VALUES (0, 1, 2)"), ConsistencyLevel.QUORUM);
> String query = withKeyspace("SELECT v FROM %s.t WHERE k IN (0, 1)
> ORDER BY c LIMIT 10");
> assertRows(cluster.coordinator(1).execute(query,
> ConsistencyLevel.ONE), row(2));
> }
> }
> {code}
> The query is returning the clustering column c as well as the regular column
> v.
> The reason for the extra column being returned is that the RowUtil is using
> ResultMessage.Rows.result.metadata.names instead on
> ResultMessage.Rows.result.metadata.requestNames(). This last method removes
> columns that have not been requested.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18892) Distributed tests can return ordering columns that have not been selected
Mike Adamson created CASSANDRA-18892:
Summary: Distributed tests can return ordering columns that have
not been selected
Key: CASSANDRA-18892
URL: https://issues.apache.org/jira/browse/CASSANDRA-18892
Project: Cassandra
Issue Type: Bug
Components: Test/dtest/java
Reporter: Mike Adamson
Assignee: Mike Adamson
The following test fails
{code:java}
@Test
public void incorrectClusteringColumnTest() throws IOException
{
try (Cluster cluster = init(Cluster.build(1).start()))
{
cluster.schemaChange(withKeyspace("CREATE TABLE %s.t (k int, c int, v
int, primary key(k, c))"));
cluster.coordinator(1).execute(withKeyspace("INSERT INTO %s.t (k, c, v)
VALUES (0, 1, 2)"), ConsistencyLevel.QUORUM);
String query = withKeyspace("SELECT v FROM %s.t WHERE k IN (0, 1) ORDER
BY c LIMIT 10");
assertRows(cluster.coordinator(1).execute(query, ConsistencyLevel.ONE),
row(2));
}
}
{code}
The query is returning the clustering column c as well as the regular column v.
The reason for the extra column being returned is that the RowUtil is using
ResultMessage.Rows.result.metadata.names instead on
ResultMessage.Rows.result.metadata.requestNames(). This last method removes
columns that have not been requested.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18808) netty-handler vulnerability: CVE-2023-4586
[
https://issues.apache.org/jira/browse/CASSANDRA-18808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770135#comment-17770135
]
Norman Maurer commented on CASSANDRA-18808:
---
Sorry I didn't have time yet but its on my todo list
> netty-handler vulnerability: CVE-2023-4586
> --
>
> Key: CASSANDRA-18808
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18808
> Project: Cassandra
> Issue Type: Bug
> Components: Consistency/Coordination
>Reporter: Brandon Williams
>Assignee: Brandon Williams
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> This is failing OWASP:
> {noformat}
> Dependency-Check Failure:
> One or more dependencies were identified with vulnerabilities that have a
> CVSS score greater than or equal to '1.0':
> netty-handler-4.1.96.Final.jar: CVE-2023-4586
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770132#comment-17770132 ] Brandon Williams commented on CASSANDRA-18891: -- I guess if that is where our appetite is at, we can call this ticket "Upgrade to JNA 5.10" and target 4.0 through trunk. > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16949) Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-16949:
Reviewers: Sam Tunnicliffe, Sam Tunnicliffe
Sam Tunnicliffe, Sam Tunnicliffe (was: Sam Tunnicliffe)
Status: Review In Progress (was: Patch Available)
> Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
> ---
>
> Key: CASSANDRA-16949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16949
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1037/workflows/c728d370-49b9-41aa-bdfb-8c41cf0355d8/jobs/6577/parallel-runs/3
> {code}
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> Tests run: 9, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 12.926 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> handleCorruptionOfLargeMessageFrame(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] null
> [junit-timeout] junit.framework.AssertionFailedError
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:484)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame(CQLConnectionTest.java:217)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testNegativeEnvelopeBodySize(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testNegativeEnvelopeBodySize(CQLConnectionTest.java:326)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testUnrecoverableMessageDecodingErrors(org.apache.cassandra.transport.CQLConnectionTest):
>FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
>
[jira] [Commented] (CASSANDRA-17092) CEP-15: Accord Beta
[
https://issues.apache.org/jira/browse/CASSANDRA-17092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770120#comment-17770120
]
Caleb Rackliffe commented on CASSANDRA-17092:
-
Making a note here, since we'll need to decide when things are clean enough to
merge, the latest Circle runs for {{cep-21-tcm}} are mentioned here:
https://issues.apache.org/jira/browse/CASSANDRA-18887?focusedCommentId=17769638=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17769638.
The immediate goal it to get to something resembling parity w/ those results.
> CEP-15: Accord Beta
> ---
>
> Key: CASSANDRA-17092
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17092
> Project: Cassandra
> Issue Type: Epic
> Components: Accord
>Reporter: Benedict Elliott Smith
>Assignee: Benedict Elliott Smith
>Priority: Normal
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRASC-73) Update token-ranges endpoint to return additional instance metadata
[ https://issues.apache.org/jira/browse/CASSANDRASC-73?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770110#comment-17770110 ] Dinesh Joshi commented on CASSANDRASC-73: - +1, thanks for the patch! > Update token-ranges endpoint to return additional instance metadata > --- > > Key: CASSANDRASC-73 > URL: https://issues.apache.org/jira/browse/CASSANDRASC-73 > Project: Sidecar for Apache Cassandra > Issue Type: Improvement > Components: Rest API >Reporter: Arjun Ashok >Assignee: Arjun Ashok >Priority: Normal > Labels: pull-request-available > > Sidecar `token-range-replicas` endpoint to return the following additional > metadata for each instance: > * State. eg Normal, Joining, Leaving > * Status. eg. Up, Down > * Address: Replica host and port > * Name: Node name resolved from the above IP address -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (4b95e9c4 -> 1ce5cedc)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 4b95e9c4 generate docs for bc8bfc13 new 1ce5cedc generate docs for bc8bfc13 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (4b95e9c4) \ N -- N -- N refs/heads/asf-staging (1ce5cedc) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. 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: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881412 -> 4881412 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-8110) Make streaming forward & backwards compatible
[
https://issues.apache.org/jira/browse/CASSANDRA-8110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770086#comment-17770086
]
Jeremy Hanna commented on CASSANDRA-8110:
-
[~yukim] is this done with what [~Bereng] did on CASSANDRA-14227?
Specifically, the {{storage_compatibility_mode}} as described in the latest
cassandra.yaml
([here|https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L2090-L2115]
is the block from cassandra.yaml):
{code:java}
# This property indicates with what Cassandra major version the storage format
will be compatible with.
#
# The chosen storage compatiblity mode will determine the versions of the
written sstables, commitlogs, hints,
# etc. Those storage elements will use the higher minor versions of the major
version that corresponds to the
# Cassandra version we want to stay compatible with. For example, if we want to
stay compatible with Cassandra 4.0
# or 4.1, the value of this property should be 4, and that will make us use
'nc' sstables.
#
# This will also determine if certain features depending on newer formats are
available. For example, extended TTLs
# up to 2106 depend on the sstable, commitlog, hints and messaging versions
that were introduced by Cassandra 5.0,
# so that feature won't be available if this property is set to CASSANDRA_4.
See upgrade guides for details. Currently
# the only supported major is CASSANDRA_4.
#
# Possible values are in the StorageCompatibilityMode.java file accessible
online. At the time of writing these are:
# - CASSANDRA_4: Stays compatible with the 4.x line in features, formats and
component versions.
# - UPGRADING: The cluster monitors nodes versions during this interim stage.
_This has a cost_ but ensures any new features,
# formats, versions, etc are enabled safely.
# - NONE: Start with all the new features and formats enabled.
#
# A typical upgrade would be:
# - Do a rolling upgrade starting all nodes in CASSANDRA_Y compatibility mode.
# - Once the new binary is rendered stable do a rolling restart with UPGRADING.
The cluster will enable new features in a safe way
# until all nodes are started in UPGRADING, then all new features are enabled.
# - Do a rolling restart with all nodes starting with NONE. This sheds the
extra cost of checking nodes versions and ensures
# a stable cluster. If a node from a previous version was started by accident
we won't any longer toggle behaviors as when UPGRADING.
#
storage_compatibility_mode: CASSANDRA_4 {code}
> Make streaming forward & backwards compatible
> -
>
> Key: CASSANDRA-8110
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8110
> Project: Cassandra
> Issue Type: New Feature
> Components: Legacy/Streaming and Messaging
>Reporter: Marcus Eriksson
>Priority: Normal
> Labels: gsoc2016, mentor
>
> To be able to seamlessly upgrade clusters we need to make it possible to
> stream files between nodes with different StreamMessage.CURRENT_VERSION
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770077#comment-17770077 ] Stefan Miklosovic edited comment on CASSANDRA-18891 at 9/28/23 2:29 PM: It would be nice to verify this (1). Maybe we could actually bump it to 5.10 (or even newer?) if it is tested on Java 17 (and update it up to trunk). (1) https://issues.apache.org/jira/browse/CASSANDRA-17019?focusedCommentId=17471224=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17471224 was (Author: smiklosovic): It would be nice to verify this (1). Maybe we could actually bump it to 5.10 (or even newer?) if it is tested on Java 17. (1) https://issues.apache.org/jira/browse/CASSANDRA-17019?focusedCommentId=17471224=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17471224 > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770077#comment-17770077 ] Stefan Miklosovic commented on CASSANDRA-18891: --- It would be nice to verify this (1). Maybe we could actually bump it to 5.10 (or even newer?) if it tested on Java 17. https://issues.apache.org/jira/browse/CASSANDRA-17019?focusedCommentId=17471224=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17471224 > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770077#comment-17770077 ] Stefan Miklosovic edited comment on CASSANDRA-18891 at 9/28/23 2:21 PM: It would be nice to verify this (1). Maybe we could actually bump it to 5.10 (or even newer?) if it is tested on Java 17. (1) https://issues.apache.org/jira/browse/CASSANDRA-17019?focusedCommentId=17471224=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17471224 was (Author: smiklosovic): It would be nice to verify this (1). Maybe we could actually bump it to 5.10 (or even newer?) if it tested on Java 17. https://issues.apache.org/jira/browse/CASSANDRA-17019?focusedCommentId=17471224=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17471224 > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770076#comment-17770076 ] Stefan Miklosovic commented on CASSANDRA-18891: --- yeah that makes sense > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770074#comment-17770074
]
Jacek Lewandowski commented on CASSANDRA-18361:
---
4.0 probably suffers from the same problem
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770073#comment-17770073
]
Jacek Lewandowski edited comment on CASSANDRA-18361 at 9/28/23 2:12 PM:
new run for 4.1:
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/953/workflows/281f3a9c-69b3-47f4-a905-c9266252bd7a
https://github.com/apache/cassandra/pull/2749
was (Author: jlewandowski):
new run for 4.1:
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/953/workflows/281f3a9c-69b3-47f4-a905-c9266252bd7a
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770073#comment-17770073
]
Jacek Lewandowski commented on CASSANDRA-18361:
---
new run for 4.1:
https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/953/workflows/281f3a9c-69b3-47f4-a905-c9266252bd7a
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770069#comment-17770069 ] Brandon Williams edited comment on CASSANDRA-18891 at 9/28/23 2:04 PM: --- The rationale for going to 4.1 in CASSANDRA-17019 was the [removal of 32 bit Darwin|https://github.com/java-native-access/jna/blob/master/CHANGES.md#breaking-changes] support. I'm not sure this is the right tradeoff; I don't think we support 32bit JVMs as it is, and the appeal of the arm64 architecture is clear. We have vetted 5.9.0 fairly well at this point so I don't think there's too much risk of regression there. was (Author: brandon.williams): The rationale for going to 4.1 in CASSANDRA-17019 was the [removal of 32 bit Darwin|https://github.com/java-native-access/jna/blob/master/CHANGES.md#breaking-changes] support. I'm not sure this is the right tradeoff; I don't think we support 32bit JVMs as it is, and the appeal of the arm64 architecture is clear. We have vetted 5.7.0 fairly well at this point so I don't think there's too much risk of regression there. > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770069#comment-17770069 ] Brandon Williams commented on CASSANDRA-18891: -- The rationale for going to 4.1 in CASSANDRA-17019 was the [removal of 32 bit Darwin|https://github.com/java-native-access/jna/blob/master/CHANGES.md#breaking-changes] support. I'm not sure this is the right tradeoff; I don't think we support 32bit JVMs as it is, and the appeal of the arm64 architecture is clear. We have vetted 5.7.0 fairly well at this point so I don't think there's too much risk of regression there. > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18742) Remove deprecated options in CompressionParams
[ https://issues.apache.org/jira/browse/CASSANDRA-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770068#comment-17770068 ] Brandon Williams commented on CASSANDRA-18742: -- +1 from me :) > Remove deprecated options in CompressionParams > -- > > Key: CASSANDRA-18742 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18742 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > These should go away (1). They were deprecated like 8 years ago in > CASSANDRA-9712 and CASSANDRA-9839. > We should also remove this (2). That is a little bit more tricky but nothing > special I would say ... > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L86-L88 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L96-L97 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18742) Remove deprecated options in CompressionParams
[ https://issues.apache.org/jira/browse/CASSANDRA-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770066#comment-17770066 ] Stefan Miklosovic commented on CASSANDRA-18742: --- OK, so I think we are done. [~brandon.williams] do you have anything to add? (ideally +1 :) ) > Remove deprecated options in CompressionParams > -- > > Key: CASSANDRA-18742 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18742 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > These should go away (1). They were deprecated like 8 years ago in > CASSANDRA-9712 and CASSANDRA-9839. > We should also remove this (2). That is a little bit more tricky but nothing > special I would say ... > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L86-L88 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L96-L97 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Williams updated CASSANDRA-18891: - Reviewers: (was: Dinesh Joshi, Stefan Miklosovic) Status: Open (was: Triage Needed) > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Steinmaurer updated CASSANDRA-18891: --- Description: As discussed on Slack: [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS Gravition instances e.g. m7g already with Cassandra 4.0. >From linked ticket: "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native binding into the C library. JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing cassandra to fail on bootstrap." was: As discussed on Slack: [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS Gravition instances e.g. m7g already with Cassandra 4.0. Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native binding into the C library. JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing cassandra to fail on bootstrap. > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > From linked ticket: > "Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. JNA 5.6.0 does not support arm64 architecture > (Apple M1 devices), causing cassandra to fail on bootstrap." -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Steinmaurer updated CASSANDRA-18891: --- Description: As discussed on Slack: [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS Gravition instances e.g. m7g already with Cassandra 4.0. Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native binding into the C library. JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing cassandra to fail on bootstrap. was: Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native binding into the C library. JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing cassandra to fail on bootstrap. Bumping the dependency to 5.9.0 adds arm64 support. Will a PR to bump the dependency be acceptable ? > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. > JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing > cassandra to fail on bootstrap. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Steinmaurer updated CASSANDRA-18891: --- Fix Version/s: 4.0.x > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.0.x > > > As discussed on Slack: > [https://the-asf.slack.com/archives/CJZLTM05A/p1684745250901489] > Created this ticket as clone of CASSANDRA-17019, to ask for considering a JNA > library upgrade in Cassandra 4.0, so that we could utilize ARM-based AWS > Gravition instances e.g. m7g already with Cassandra 4.0. > Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. > JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing > cassandra to fail on bootstrap. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Steinmaurer updated CASSANDRA-18891: --- Fix Version/s: (was: 4.1-alpha1) > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > > Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. > JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing > cassandra to fail on bootstrap. > Bumping the dependency to 5.9.0 adds arm64 support. Will a PR to bump the > dependency be acceptable ? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Assigned] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Steinmaurer reassigned CASSANDRA-18891: -- Assignee: (was: Yuqi Gu) > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > Fix For: 4.1-alpha1 > > > Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. > JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing > cassandra to fail on bootstrap. > Bumping the dependency to 5.9.0 adds arm64 support. Will a PR to bump the > dependency be acceptable ? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
Thomas Steinmaurer created CASSANDRA-18891: -- Summary: Cassandra 4.0 - JNA 5.6.0 does not support arm64 Key: CASSANDRA-18891 URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 Project: Cassandra Issue Type: Bug Components: Dependencies Reporter: Thomas Steinmaurer Assignee: Yuqi Gu Fix For: 4.1-alpha1 Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native binding into the C library. JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing cassandra to fail on bootstrap. Bumping the dependency to 5.9.0 adds arm64 support. Will a PR to bump the dependency be acceptable ? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18891) Cassandra 4.0 - JNA 5.6.0 does not support arm64
[ https://issues.apache.org/jira/browse/CASSANDRA-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Thomas Steinmaurer updated CASSANDRA-18891: --- Source Control Link: (was: https://github.com/apache/cassandra/commit/2043cb9fb6b25ff34afb90467b9476a09acc3933) > Cassandra 4.0 - JNA 5.6.0 does not support arm64 > > > Key: CASSANDRA-18891 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18891 > Project: Cassandra > Issue Type: Bug > Components: Dependencies >Reporter: Thomas Steinmaurer >Priority: Normal > > Cassandra depends on net.java.dev.jna.jna version 5.6.0 to do the native > binding into the C library. > JNA 5.6.0 does not support arm64 architecture (Apple M1 devices), causing > cassandra to fail on bootstrap. > Bumping the dependency to 5.9.0 adds arm64 support. Will a PR to bump the > dependency be acceptable ? -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770060#comment-17770060
]
Jacek Lewandowski commented on CASSANDRA-18361:
---
In 4.1 {{ReducedKeyIterator}} is initialized lazily, that's why I've initially
claimed that the flaky test does not affect 4.1. Though there is a problem with
it:
{code:java}
Future submitIndexBuild(final SecondaryIndexBuilder builder,
ActiveCompactionsTracker activeCompactions)
{
Runnable runnable = new Runnable()
{
public void run()
{
activeCompactions.beginCompaction(builder);
try
{
builder.build();
}
finally
{
activeCompactions.finishCompaction(builder);
}
}
};
return executor.submitIfRunning(runnable, "index build");
}
{code}
now - the {{builder.build()}} method is supposed to close the key iterator in
finally block. Since the key iterator internally initialized lazily, it will
not close if it was not initialized yet; then,
{{activeCompactions.finishCompaction()}} accesses the key iterator and
initializes it, and there is no place for it to be closed. In fact, if no
exception is thrown, {{finishCompaction}} accesses a closed iterator, which imo
bad anyway.
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770035#comment-17770035
]
Jacek Lewandowski edited comment on CASSANDRA-18361 at 9/28/23 1:23 PM:
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/952/workflows/e61b7ff9-9003-4020-bc74-ad4349acf2ad]
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/950/workflows/7d2d3b23-04b0-4fb7-befd-20ef288f9d10]
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/951/workflows/84600429-680b-4676-8bb5-12d9ac550a1f]
-The issue does not affect 4.0 and 4.1-
UPDATE: In 4.1 there is a bug in the code which the test helped to reveal
was (Author: jlewandowski):
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/952/workflows/e61b7ff9-9003-4020-bc74-ad4349acf2ad]
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/950/workflows/7d2d3b23-04b0-4fb7-befd-20ef288f9d10]
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/951/workflows/84600429-680b-4676-8bb5-12d9ac550a1f]
The issue does not affect 4.0 and 4.1
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18881) Test failure: org.apache.cassandra.tools.nodetool.ForceCompactionTest.forceCompactMultipleRowsTombstoneTest-.jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-18881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770049#comment-17770049
]
Berenguer Blasi commented on CASSANDRA-18881:
-
Test setup delayed flushes could create extra sstables. The test's compactions
being targeted to a subset of keys can only compact some of the sstables and
some could be left behind. A major compaction, which the test already had a
note about
[already|https://github.com/apache/cassandra/pull/2738/files#diff-769f7f7b025f1c1aa9f79f3d57c7249c2507352b43036a03f532e443912c984dR253]
(line above), solves that. Then sstable file deletion happens on a scheduled
runner and we want to spinAssert on that.
It was easy to repro on 5K repeats and passes with the fix.
> Test failure:
> org.apache.cassandra.tools.nodetool.ForceCompactionTest.forceCompactMultipleRowsTombstoneTest-.jdk11
>
> ---
>
> Key: CASSANDRA-18881
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18881
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.x
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1718/testReport/org.apache.cassandra.tools.nodetool/ForceCompactionTest/forceCompactMultipleRowsTombstoneTest__jdk11/]
> h3.
> {code:java}
> Stacktrace
> junit.framework.AssertionFailedError at
> org.apache.cassandra.tools.nodetool.ForceCompactionTest.verifyNotContainsTombstones(ForceCompactionTest.java:251)
> at
> org.apache.cassandra.tools.nodetool.ForceCompactionTest.forceCompactMultipleRowsTombstoneTest(ForceCompactionTest.java:129)
> 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)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18881) Test failure: org.apache.cassandra.tools.nodetool.ForceCompactionTest.forceCompactMultipleRowsTombstoneTest-.jdk11
[
https://issues.apache.org/jira/browse/CASSANDRA-18881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Berenguer Blasi updated CASSANDRA-18881:
Test and Documentation Plan: See PR
Status: Patch Available (was: In Progress)
> Test failure:
> org.apache.cassandra.tools.nodetool.ForceCompactionTest.forceCompactMultipleRowsTombstoneTest-.jdk11
>
> ---
>
> Key: CASSANDRA-18881
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18881
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Ekaterina Dimitrova
>Assignee: Berenguer Blasi
>Priority: Normal
> Fix For: 5.x
>
>
> [https://ci-cassandra.apache.org/job/Cassandra-trunk/1718/testReport/org.apache.cassandra.tools.nodetool/ForceCompactionTest/forceCompactMultipleRowsTombstoneTest__jdk11/]
> h3.
> {code:java}
> Stacktrace
> junit.framework.AssertionFailedError at
> org.apache.cassandra.tools.nodetool.ForceCompactionTest.verifyNotContainsTombstones(ForceCompactionTest.java:251)
> at
> org.apache.cassandra.tools.nodetool.ForceCompactionTest.forceCompactMultipleRowsTombstoneTest(ForceCompactionTest.java:129)
> 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)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770035#comment-17770035
]
Jacek Lewandowski commented on CASSANDRA-18361:
---
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/952/workflows/e61b7ff9-9003-4020-bc74-ad4349acf2ad]
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/950/workflows/7d2d3b23-04b0-4fb7-befd-20ef288f9d10]
[https://app.circleci.com/pipelines/github/jacek-lewandowski/cassandra/951/workflows/84600429-680b-4676-8bb5-12d9ac550a1f]
The issue does not affect 4.0 and 4.1
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18742) Remove deprecated options in CompressionParams
[ https://issues.apache.org/jira/browse/CASSANDRA-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770029#comment-17770029 ] Maxim Muzafarov edited comment on CASSANDRA-18742 at 9/28/23 12:09 PM: --- went through all the changes and the code base to make sure we didn't miss anything, it looks like everything is correct, so I'm +1 (nb) I left a minor comment, but we can live without fixing it. :-) was (Author: mmuzaf): went through all the changes and the code base to make sure we didn't miss anything, it looks like everything is correct, so I'm +1 (nb) > Remove deprecated options in CompressionParams > -- > > Key: CASSANDRA-18742 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18742 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > These should go away (1). They were deprecated like 8 years ago in > CASSANDRA-9712 and CASSANDRA-9839. > We should also remove this (2). That is a little bit more tricky but nothing > special I would say ... > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L86-L88 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L96-L97 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18742) Remove deprecated options in CompressionParams
[ https://issues.apache.org/jira/browse/CASSANDRA-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770029#comment-17770029 ] Maxim Muzafarov commented on CASSANDRA-18742: - went through all the changes and the code base to make sure we didn't miss anything, it looks like everything is correct, so I'm +1 (nb) > Remove deprecated options in CompressionParams > -- > > Key: CASSANDRA-18742 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18742 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 1h 20m > Remaining Estimate: 0h > > These should go away (1). They were deprecated like 8 years ago in > CASSANDRA-9712 and CASSANDRA-9839. > We should also remove this (2). That is a little bit more tricky but nothing > special I would say ... > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L86-L88 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L96-L97 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18876) The vector data type shouldn't support empty value
[
https://issues.apache.org/jira/browse/CASSANDRA-18876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770027#comment-17770027
]
Andres de la Peña commented on CASSANDRA-18876:
---
The runs above contained some failures that have disappeared after rebase:
||PR||CI||
|[5.0
|https://github.com/apache/cassandra/pull/2723]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3219/workflows/f1fc8fbb-392a-4a7f-96b7-69f410c7a184]
[j17|https://app.circleci.com/pipelines/github/adelapena/cassandra/3219/workflows/f5cd0f4e-b6a9-45a9-9355-c34d167a8894]|
|[trunk|https://github.com/apache/cassandra/pull/2746]|[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/3218/workflows/ecd5d789-b275-4418-9712-f36f92fae828]
[j17|https://app.circleci.com/pipelines/github/adelapena/cassandra/3218/workflows/5b52cead-e0e8-4e95-bded-45b139fbbbf6]|
All green except for two unrelated failures on {{{}trunk{}}}:
* {{o.a.c.index.sasi.disk.OnDiskIndexTest#testSparseMode}} is CASSANDRA-13169
* {{o.a.c.repair.ConcurrentIrWithPreviewFuzzTest#concurrentIrWithPreview}} is
CASSANDRA-18890
[~dcapwell] do you have any opinion [on this
discussion|https://github.com/apache/cassandra/pull/2746#discussion_r1339458277]?
> The vector data type shouldn't support empty value
> --
>
> Key: CASSANDRA-18876
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18876
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Vector Search
>Reporter: Andres de la Peña
>Assignee: Andres de la Peña
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> As discussed on [the mail
> list|https://lists.apache.org/thread/qq0jkm6rlkd2slfmhgz7om14tbpys891], the
> vector data type shouldn't allow empty values.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770026#comment-17770026
]
Jacek Lewandowski commented on CASSANDRA-18361:
---
I'm not going to fix the original issue in this ticket; I can create one to try
to fix it for 5.0 and on, but I think we should not touch pre 5.0. I'll verify
if the issue exists in the previous versions
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770023#comment-17770023
]
Andres de la Peña commented on CASSANDRA-18890:
---
CC [~dcapwell] [~maedhroz] [~marcuse]
> Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
> -
>
> Key: CASSANDRA-18890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
>
> The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
> is flaky in both 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
> {code}
> junit.framework.AssertionFailedError: Property error detected:
> Seed = 3695691971125975155
> Examples = 2
> Pure = false
> Error: property test did not complete within PT1M
> Values:
> at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
> at accord.utils.Property$SingleBuilder.check(Property.java:223)
> at accord.utils.Property$ForBuilder.check(Property.java:124)
> at
> org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is around 6%. The CircleCI runs above have been generated with:
> {code}
> .circleci/generate.sh -p -s \
> -e
> REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
> -e REPEATED_UTESTS_COUNT=500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18816) Add support for repair coordinator to retry messages that timeout
[
https://issues.apache.org/jira/browse/CASSANDRA-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770022#comment-17770022
]
Andres de la Peña commented on CASSANDRA-18816:
---
The new {{ConcurrentIrWithPreviewFuzzTest}} introduced by this patch is ~6%
flaky in both 5.0 and trunk:
*
https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
*
https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
{code}
junit.framework.AssertionFailedError: Property error detected:
Seed = 3695691971125975155
Examples = 2
Pure = false
Error: property test did not complete within PT1M
Values:
at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
at accord.utils.Property$SingleBuilder.check(Property.java:223)
at accord.utils.Property$ForBuilder.check(Property.java:124)
at
org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{code}
I don't see any repeated runs on the CI results above, were they run?
I have opened CASSANDRA-18890 to deal with it.
> Add support for repair coordinator to retry messages that timeout
> -
>
> Key: CASSANDRA-18816
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18816
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Repair
>Reporter: David Capwell
>Assignee: David Capwell
>Priority: Normal
> Fix For: 5.0-alpha2
>
> Time Spent: 13h 10m
> Remaining Estimate: 0h
>
> Now that CASSANDRA-15399 is in, most of the repair messages have a state that
> they can check against to make message delivery idempotent, allowing the
> coordinator to retry such messages; a few of the most critical messages to
> retry are: PREPARE_MSG, VALIDATION_REQ, VALIDATION_RSP, SYNC_REQ, and
> SYNC_RSP.
> With this I propose making the coordinator able to retry these key messages
> to try and make repair more resilient to ephemeral issues.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
[
https://issues.apache.org/jira/browse/CASSANDRA-18890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18890:
--
Bug Category: Parent values: Correctness(12982)Level 1 values: Test
Failure(12990)
> Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
> -
>
> Key: CASSANDRA-18890
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Andres de la Peña
>Priority: Normal
>
> The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
> is flaky in both 5.0 and trunk:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
> {code}
> junit.framework.AssertionFailedError: Property error detected:
> Seed = 3695691971125975155
> Examples = 2
> Pure = false
> Error: property test did not complete within PT1M
> Values:
> at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
> at accord.utils.Property$SingleBuilder.check(Property.java:223)
> at accord.utils.Property$ForBuilder.check(Property.java:124)
> at
> org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> {code}
> Flakiness is around 6%. The CircleCI runs above have been generated with:
> {code}
> .circleci/generate.sh -p -s \
> -e
> REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
> -e REPEATED_UTESTS_COUNT=500
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Created] (CASSANDRA-18890) Test failure: org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
Andres de la Peña created CASSANDRA-18890:
-
Summary: Test failure:
org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest
Key: CASSANDRA-18890
URL: https://issues.apache.org/jira/browse/CASSANDRA-18890
Project: Cassandra
Issue Type: Bug
Components: Test/unit
Reporter: Andres de la Peña
The unit test {{org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest}}
is flaky in both 5.0 and trunk:
*
https://app.circleci.com/pipelines/github/adelapena/cassandra/3222/workflows/ecfca708-f183-429e-80e5-b2bfea8d25a0/jobs/80292/tests
*
https://app.circleci.com/pipelines/github/adelapena/cassandra/3221/workflows/bb777ac0-6263-4d6e-aa54-35d6928e1e9b/jobs/80294
{code}
junit.framework.AssertionFailedError: Property error detected:
Seed = 3695691971125975155
Examples = 2
Pure = false
Error: property test did not complete within PT1M
Values:
at accord.utils.Property$Common.checkWithTimeout(Property.java:115)
at accord.utils.Property$SingleBuilder.check(Property.java:223)
at accord.utils.Property$ForBuilder.check(Property.java:124)
at
org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest.concurrentIrWithPreview(ConcurrentIrWithPreviewFuzzTest.java:46)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
{code}
Flakiness is around 6%. The CircleCI runs above have been generated with:
{code}
.circleci/generate.sh -p -s \
-e
REPEATED_UTESTS=org.apache.cassandra.repair.ConcurrentIrWithPreviewFuzzTest \
-e REPEATED_UTESTS_COUNT=500
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769997#comment-17769997
]
Andres de la Peña commented on CASSANDRA-18361:
---
Probably nothing, but there can always be surprises. That's why we run them
with both configs on CI. The 500 runs can be divided with 250 in vnodes and 250
in no-vnodes.
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra-website] branch asf-staging updated (819a63098 -> 4b95e9c4c)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-staging in repository https://gitbox.apache.org/repos/asf/cassandra-website.git discard 819a63098 generate docs for bc8bfc13 new 4b95e9c4c generate docs for bc8bfc13 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (819a63098) \ N -- N -- N refs/heads/asf-staging (4b95e9c4c) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. 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: content/search-index.js | 2 +- site-ui/build/ui-bundle.zip | Bin 4881412 -> 4881412 bytes 2 files changed, 1 insertion(+), 1 deletion(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769995#comment-17769995
]
Jacek Lewandowski commented on CASSANDRA-18361:
---
what vnodes have to do with it?
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-16949) Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-16949:
--
Test and Documentation Plan: run repeated tests
Status: Patch Available (was: In Progress)
> Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
> ---
>
> Key: CASSANDRA-16949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16949
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.x
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1037/workflows/c728d370-49b9-41aa-bdfb-8c41cf0355d8/jobs/6577/parallel-runs/3
> {code}
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> Tests run: 9, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 12.926 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> handleCorruptionOfLargeMessageFrame(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] null
> [junit-timeout] junit.framework.AssertionFailedError
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:484)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame(CQLConnectionTest.java:217)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testNegativeEnvelopeBodySize(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testNegativeEnvelopeBodySize(CQLConnectionTest.java:326)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testUnrecoverableMessageDecodingErrors(org.apache.cassandra.transport.CQLConnectionTest):
>FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testUnrecoverableMessageDecodingErrors(CQLConnectionTest.java:392)
>
[jira] [Commented] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769978#comment-17769978
]
Andres de la Peña commented on CASSANDRA-18361:
---
The fix looks good to me. We will also need 500-iteration runs for all branches
since 4.0, with and without vnodes.
{quote}I'm not very happy with the solution. I think we should modify the code
so that the iterator is opened only in the place where it can be closed -
instead of passing the ad-hoc initialized key iterator to the builder and
assuming that {{build}} method will be called, we should rather initialize the
iterator inside the {{build}} method, where the iterator is closed in the
{{finally}} block.
{quote}
Is it the plan to do it here or on a separate ticket?
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andres de la Peña updated CASSANDRA-18361:
--
Reviewers: Andres de la Peña, Andres de la Peña (was: Andres de la Peña)
Andres de la Peña, Andres de la Peña (was: Andres de la Peña)
Status: Review In Progress (was: Patch Available)
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18161) Test Failure: org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame
[
https://issues.apache.org/jira/browse/CASSANDRA-18161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-18161:
--
Resolution: Duplicate
Status: Resolved (was: Open)
> Test Failure:
> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame
> --
>
> Key: CASSANDRA-18161
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18161
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: Michael Semb Wever
>Priority: Normal
> Fix For: 4.0.x, 4.1.x, 5.x
>
>
> Flaky.
> {noformat}
> junit.framework.AssertionFailedError
> at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:491)
> at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:450)
> at
> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame(CQLConnectionTest.java:221)
> 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)
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16999) system.peers and system.peers_v2 do not contain the native_transport and/or native_transport_port_ssl
[ https://issues.apache.org/jira/browse/CASSANDRA-16999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769948#comment-17769948 ] Stefan Miklosovic commented on CASSANDRA-16999: --- I put some comments to [~brandon.williams]'s PR. It would be great to get a confirmation this makes sense to do from the perspective of [~absurdfarce] before actually merging this. > system.peers and system.peers_v2 do not contain the native_transport and/or > native_transport_port_ssl > - > > Key: CASSANDRA-16999 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16999 > Project: Cassandra > Issue Type: Bug > Components: Local/Other >Reporter: Steve Lacerda >Assignee: Brandon Williams >Priority: Normal > Fix For: 4.0.x, 4.1.x, 5.x > > > system.peers_v2 includes a “native_port” but has no notion of > native_transport_port vs. native_transport_port_ssl. Given this limited > information, there’s no clear way for the driver to know that different ports > are being used for SSL vs. non-SSL or which of those two ports is identified > by “native_port”. > > The issue we ran into is that the java driver, since it has no notion of the > transport port SSL, the driver was only using the contact points and was not > load balancing. > > The customer had both set: > native_transport_port: 9042 > native_transport_port_ssl: 9142 > > They were attempting to connect to 9142, but that was failing. They could > only use 9042, and so their applications load balancing was failing. We found > that any node that was a contact point was connecting, but the other nodes > were never acting as coordinators. > > There are still issues in the driver, for which I have created JAVA-2967, > which also refers to JAVA-2638, but the system.peers and system.peers_v2 > tables should both contain native_transport_port and > native_transport_port_ssl. > > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18861) add time elapsed for simple CQL statement in the cql shell
[ https://issues.apache.org/jira/browse/CASSANDRA-18861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769943#comment-17769943 ] Ling Mao commented on CASSANDRA-18861: -- Thanks all for pushing this ticket:) > add time elapsed for simple CQL statement in the cql shell > -- > > Key: CASSANDRA-18861 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18861 > Project: Cassandra > Issue Type: Improvement > Components: CQL/Interpreter >Reporter: Ling Mao >Assignee: Ling Mao >Priority: Low > Fix For: 5.1 > > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-18742) Remove deprecated options in CompressionParams
[ https://issues.apache.org/jira/browse/CASSANDRA-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769940#comment-17769940 ] Stefan Miklosovic commented on CASSANDRA-18742: --- https://github.com/apache/cassandra/pull/2699/files#r1339690523 https://github.com/apache/cassandra/pull/2699/commits/fc2fc26d4d8fc0d2d34ca660c348aef90b8973ce > Remove deprecated options in CompressionParams > -- > > Key: CASSANDRA-18742 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18742 > Project: Cassandra > Issue Type: Task > Components: Feature/Compression >Reporter: Stefan Miklosovic >Assignee: Stefan Miklosovic >Priority: Normal > Fix For: 5.x > > Time Spent: 1h > Remaining Estimate: 0h > > These should go away (1). They were deprecated like 8 years ago in > CASSANDRA-9712 and CASSANDRA-9839. > We should also remove this (2). That is a little bit more tricky but nothing > special I would say ... > (1) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L86-L88 > (2) > https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/schema/CompressionParams.java#L96-L97 -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-18887) CEP-21 - Implement missing features and various other fixes
[ https://issues.apache.org/jira/browse/CASSANDRA-18887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769638#comment-17769638 ] Marcus Eriksson edited comment on CASSANDRA-18887 at 9/28/23 7:33 AM: -- https://app.circleci.com/pipelines/github/krummas/cassandra/902/workflows/2f245ab5-801c-443e-b3a7-4205dc1c0026 23 failing unit tests 27 failing python dtests 11 failing jvm dtests was (Author: krummas): https://app.circleci.com/pipelines/github/krummas/cassandra/901/workflows/9708e318-1eec-4678-9bf2-1faf6beb0b19 23 failing unit tests 43 failing python dtests 11 failing jvm dtests > CEP-21 - Implement missing features and various other fixes > --- > > Key: CASSANDRA-18887 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18887 > Project: Cassandra > Issue Type: Improvement > Components: Consistency/Coordination >Reporter: Marcus Eriksson >Assignee: Marcus Eriksson >Priority: Normal > > [CEP-21] fix cqlshlib tests > https://github.com/krummas/cassandra/commit/31a4f59449 > Add cluster_metadata keyspace where needed > [CEP-21] remove authsetup > https://github.com/krummas/cassandra/commit/4cab51d76b > Avoid calling doAuthSetup twice > [CEP-21] serialize MemtableParams when writing TableParams > https://github.com/krummas/cassandra/commit/602c01a7b4 > Missed in earlier rebase, need to serialize MemtableParams when saving a > snapshot > [CEP-21] Upgrading a one node cluster to TCM fails attempting Gossip shadow > round > https://github.com/krummas/cassandra/commit/3feb3b1a58 > Upgrading fails due to first upgraded node waiting for gossip state from > peers. > [CEP-21] Implement replacement with same address > https://github.com/krummas/cassandra/commit/a05bbc4870 > Add back missing replace with same address feature > [CEP-21] fix nodetool bootstrap resume > https://github.com/krummas/cassandra/commit/061b835dae > Add back missing nodetool bootstrap resume feature > [CEP-21] Remove LEFT peers from system tables and exclude them during startup > https://github.com/krummas/cassandra/commit/4bc9dc674b > Avoid trying to gossip with LEFT peers > [CEP-21] Fix flaky distributed log test. While it fails very infrequently on > CI, it consistently fails locally. > https://github.com/krummas/cassandra/commit/f231e9dda9 > Test fix > [CEP-21] Retry indefinitely for STARTUP messages. > https://github.com/krummas/cassandra/commit/7f9e88857e > If the CMS is down and we try to upgrade an instance we should block until > the CMS comes back > [CEP-21] Implement versioning for ranges > https://github.com/krummas/cassandra/commit/a170b9f349 > To be able to know if the coordinator has the correct ring view we keep track > of when a range was last updated. If coordinator has not seen this update we > fail the request. > [CEP-21] Handle case where removenode requires no streaming to restore RF > https://github.com/krummas/cassandra/commit/68054d3ec0 > [CEP-21] Remove redundant Keyspaces arg from SchemaTransformation::apply > https://github.com/krummas/cassandra/commit/fe1c132946 > Code cleanup > [CEP-21] Don't trigger client warnings or guardrails when executing > AlterSchema transformations > https://github.com/krummas/cassandra/commit/dbbd96c9ad > Avoid getting multiple client warnings > [CEP-21] Validate schema alterations on coordinator > https://github.com/krummas/cassandra/commit/4711053513 > [CEP-21] Add a script for simulation running > https://github.com/krummas/cassandra/commit/94543e9230 > [CEP-21] Add nextId to Directory serialization and make it possible to bump > metadata serialization version > https://github.com/krummas/cassandra/commit/6d5d6a8bc6 > Previously, on bounce, each instance calculated which nodeId we should give a > new node by counting the number of instances in the cluster, this can diverge > so that different nodes have different ids. Fixed by serializing the current > nextId when storing snapshot. > [CEP-21] Add metric for CMS membership > https://github.com/krummas/cassandra/commit/bbdd165013 > [CEP-21] Reenable starting without joining (-Dcassandra.join_ring=false) > https://github.com/krummas/cassandra/commit/565c3747c5 > Add back missing join_ring=false feature. > [CEP-21] Preparing DDL statements should capture the CQL string > https://github.com/krummas/cassandra/commit/4608a74c64 > Avoid NPE -- This message was sent by Atlassian Jira (v8.20.10#820010) - 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 for CASSANDRA-18827
This is an automated email from the ASF dual-hosted git repository. smiklosovic 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 fbf6508940 ninja fix for CASSANDRA-18827 fbf6508940 is described below commit fbf650894035e90e556f13a9ca3f5efdcda8571f Author: Stefan Miklosovic AuthorDate: Thu Sep 28 09:02:44 2023 +0200 ninja fix for CASSANDRA-18827 --- pylib/setup.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pylib/setup.py b/pylib/setup.py index 8fdca11e16..1dfd8cdc89 100755 --- a/pylib/setup.py +++ b/pylib/setup.py @@ -16,7 +16,7 @@ # limitations under the License. import sys -from setuptools import setup +from distutils.core import setup def get_extensions(): - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-16949) Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769930#comment-17769930
]
Jacek Lewandowski commented on CASSANDRA-16949:
---
alternatively, if we want to reliably verify the error message is sent, we can
use byteman and not rely the client receiving it - this is probably a simpler
approach and we verify exactly what we want to verify.
> Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
> ---
>
> Key: CASSANDRA-16949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16949
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.x
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1037/workflows/c728d370-49b9-41aa-bdfb-8c41cf0355d8/jobs/6577/parallel-runs/3
> {code}
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> Tests run: 9, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 12.926 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> handleCorruptionOfLargeMessageFrame(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] null
> [junit-timeout] junit.framework.AssertionFailedError
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:484)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame(CQLConnectionTest.java:217)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testNegativeEnvelopeBodySize(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testNegativeEnvelopeBodySize(CQLConnectionTest.java:326)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testUnrecoverableMessageDecodingErrors(org.apache.cassandra.transport.CQLConnectionTest):
>FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout]
[jira] [Commented] (CASSANDRA-18798) Appending to list in Accord transactions uses insertion timestamp
[
https://issues.apache.org/jira/browse/CASSANDRA-18798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769929#comment-17769929
]
Jaroslaw Kijanowski commented on CASSANDRA-18798:
-
After applying [the
patch|https://gist.githubusercontent.com/kijanowski/31e9534467d2c96ac3fcc7e9fff50465/raw/d6b0514c34dcd193e154d49184cd956909aac157/list-order.patch]
the anomaly is still present. For register "1":
{code:java}
{:type :ok, :process 2, :value [[:r 3 []] [:r 1 []]], :tid 0, :n 1, :time
1695883304794618396}
{:type :ok, :process 3, :value [[:append 1 2001] [:append 4 2002]], :tid 4, :n
1, :time 1695883304832554708}
{:type :ok, :process 7, :value [[:r 1 [2001]]], :tid 1, :n 1, :time
1695883304854012471}
{:type :ok, :process 1, :value [[:append 1 4501]], :tid 9, :n 1, :time
1695883304869167769}
{:type :ok, :process 6, :value [[:r 4 [2002]] [:append 1 1501]], :tid 3, :n 1,
:time 1695883304885126603}
{:type :ok, :process 2, :value [[:r 1 [4501 2001 1501]] [:append 5 1]], :tid 0,
:n 2, :time 1695883305831707192} {code}
Process 7 reads 2001 and then process 2 reads 4501 2001 1501.
sstable dump output:
{code:java}
[1]@5724 Row[info=[ts=-9223372036854775808] ]: | ,
[contents[17b726c0-5dca-11ee-a720-095e87595144]=4501 ts=1695883305918000],
[contents[17b774e0-5dca-11ee-a7e1-9776011062ce]=2001 ts=1695883305913000],
[contents[17b774ea-5dca-11ee-a7e1-9776011062ce]=1501 ts=1695883305922000],
... {code}
Based on the timestamps 2001 should come before 4501.
> Appending to list in Accord transactions uses insertion timestamp
> -
>
> Key: CASSANDRA-18798
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18798
> Project: Cassandra
> Issue Type: Bug
> Components: Accord
>Reporter: Jaroslaw Kijanowski
>Assignee: Henrik Ingo
>Priority: Normal
> Attachments: image-2023-09-26-20-05-25-846.png
>
>
> Given the following schema:
> {code:java}
> CREATE KEYSPACE IF NOT EXISTS accord WITH replication = {'class':
> 'SimpleStrategy', 'replication_factor': 3};
> CREATE TABLE IF NOT EXISTS accord.list_append(id int PRIMARY KEY,contents
> LIST);
> TRUNCATE accord.list_append;{code}
> And the following two possible queries executed by 10 threads in parallel:
> {code:java}
> BEGIN TRANSACTION
> LET row = (SELECT * FROM list_append WHERE id = ?);
> SELECT row.contents;
> COMMIT TRANSACTION;"
> BEGIN TRANSACTION
> UPDATE list_append SET contents += ? WHERE id = ?;
> COMMIT TRANSACTION;"
> {code}
> there seems to be an issue with transaction guarantees. Here's an excerpt in
> the edn format from a test.
> {code:java}
> {:type :invoke :process 8 :value [[:append 5 352]] :tid 3 :n 52
> :time 1692607285967116627}
> {:type :invoke :process 9 :value [[:r 5 nil]] :tid 1 :n 54
> :time 1692607286078732473}
> {:type :invoke :process 6 :value [[:append 5 553]] :tid 5 :n 53
> :time 1692607286133833428}
> {:type :invoke :process 7 :value [[:append 5 455]] :tid 4 :n 55
> :time 1692607286149702511}
> {:type :ok :process 8 :value [[:append 5 352]] :tid 3 :n 52
> :time 1692607286156314099}
> {:type :invoke :process 5 :value [[:r 5 nil]] :tid 9 :n 52
> :time 1692607286167090389}
> {:type :ok :process 9 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352]]] :tid 1 :n 54 :time 1692607286168657534}
> {:type :invoke :process 1 :value [[:r 5 nil]] :tid 0 :n 51
> :time 1692607286201762938}
> {:type :ok :process 7 :value [[:append 5 455]] :tid 4 :n 55
> :time 1692607286245571513}
> {:type :invoke :process 7 :value [[:r 5 nil]] :tid 4 :n 56
> :time 1692607286245655775}
> {:type :ok :process 5 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352 455]]] :tid 9 :n 52 :time 1692607286253928906}
> {:type :invoke :process 5 :value [[:r 5 nil]] :tid 9 :n 53
> :time 1692607286254095215}
> {:type :ok :process 6 :value [[:append 5 553]] :tid 5 :n 53
> :time 1692607286266263422}
> {:type :ok :process 1 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419 19 623 22 425 24 926 25 832 130 733 430 533 29 933 333
> 537 934 538 740 139 744 938 544 42 646 749 242 546 547 548 753 450 150 349 48
> 852 352 553 455]]] :tid 0 :n 51 :time 1692607286271617955}
> {:type :ok :process 7 :value [[:r 5 [303 304 604 6 306 509 909 409 912
> 411 514 415 719 419
[jira] [Commented] (CASSANDRA-16949) Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
[
https://issues.apache.org/jira/browse/CASSANDRA-16949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769926#comment-17769926
]
Sam Tunnicliffe commented on CASSANDRA-16949:
-
That doesn't sound unreasonable. I think it's a nice property of the test to
_not_ rely on it being the last sent frame that's corrupt, but obviously that's
invalidated if it makes the test unreliable.
> Fix flaky test org.apache.cassandra.transport.CQLConnectionTest
> ---
>
> Key: CASSANDRA-16949
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16949
> Project: Cassandra
> Issue Type: Bug
> Components: Test/unit
>Reporter: David Capwell
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.x
>
>
> https://app.circleci.com/pipelines/github/dcapwell/cassandra/1037/workflows/c728d370-49b9-41aa-bdfb-8c41cf0355d8/jobs/6577/parallel-runs/3
> {code}
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> [junit-timeout] Testsuite: org.apache.cassandra.transport.CQLConnectionTest
> Tests run: 9, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 12.926 sec
> [junit-timeout]
> [junit-timeout] Testcase:
> handleCorruptionOfLargeMessageFrame(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] null
> [junit-timeout] junit.framework.AssertionFailedError
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:484)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame(CQLConnectionTest.java:217)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testNegativeEnvelopeBodySize(org.apache.cassandra.transport.CQLConnectionTest):
> FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:446)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testNegativeEnvelopeBodySize(CQLConnectionTest.java:326)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [junit-timeout]
> [junit-timeout]
> [junit-timeout] Testcase:
> testUnrecoverableMessageDecodingErrors(org.apache.cassandra.transport.CQLConnectionTest):
>FAILED
> [junit-timeout] expected:<[]0L> but was:<[52424]0L>
> [junit-timeout] junit.framework.AssertionFailedError: expected:<[]0L> but
> was:<[52424]0L>
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> [junit-timeout] at
> java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> [junit-timeout] at
> java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest$AllocationObserver.lambda$verifier$0(CQLConnectionTest.java:850)
> [junit-timeout] at
> org.apache.cassandra.transport.CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:492)
> [junit-timeout] at
>
[jira] [Updated] (CASSANDRA-18361) Test Failure: secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
[
https://issues.apache.org/jira/browse/CASSANDRA-18361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacek Lewandowski updated CASSANDRA-18361:
--
Reviewers: Andres de la Peña
> Test Failure:
> secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
>
>
> Key: CASSANDRA-18361
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18361
> Project: Cassandra
> Issue Type: Bug
> Components: Test/dtest/python
>Reporter: Andres de la Peña
>Assignee: Jacek Lewandowski
>Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> The Python dtest
> {{secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index}}
> is flaky, at least for trunk:
> *
> https://butler.cassandra.apache.org/#/ci/upstream/workflow/Cassandra-trunk/failure/secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index
> *
> https://ci-cassandra.apache.org/job/Cassandra-trunk/1501/testReport/dtest.secondary_indexes_test/TestSecondaryIndexes/test_failing_manual_rebuild_index/
> {code}
> Error Message
> failed on teardown with "Unexpected error found in node logs (see stdout for
> full details). Errors: [[node1] 'ERROR [Reference-Reaper] 2023-03-23
> 00:23:43,597 Ref.java:237 - LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']"
> Stacktrace
> Unexpected error found in node logs (see stdout for full details). Errors:
> [[node1] 'ERROR [Reference-Reaper] 2023-03-23 00:23:43,597 Ref.java:237 -
> LEAK DETECTED: a reference (class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db)
> to class
> org.apache.cassandra.io.util.FileHandle$Cleanup@967019010:/home/cassandra/cassandra/cassandra-dtest/tmp/dtest-hgjoy8rq/test/node1/data0/k/t-b7dae870c91011eda58f05bc40bfcaa1/nc-1-big-Index.db
> was not released before the reference was garbage collected']
> {code}
> The failure can be reproduced in CircleCI:
> *
> https://app.circleci.com/pipelines/github/adelapena/cassandra/2732/workflows/829434ab-2d1a-4e1c-8c7f-42449fcfda22
> The CircleCI config I used to reproduce the test failure can be generated
> with:
> {code}
> .circleci/generate.sh -p \
> -e REPEATED_DTESTS_COUNT=200 \
> -e
> REPEATED_DTESTS=secondary_indexes_test.py::TestSecondaryIndexes::test_failing_manual_rebuild_index
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18884) Test failure: org.apache.cassandra.db.compaction.LongCompactionsTest
[ https://issues.apache.org/jira/browse/CASSANDRA-18884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Lewandowski updated CASSANDRA-18884: -- Fix Version/s: 5.0 5.1 (was: 5.x) (was: 5.0.x) Since Version: 5.0-alpha1 Source Control Link: https://github.com/apache/cassandra/commit/6de90bf75c2a5138f4ed72ff6ed588dc180e8a9d Resolution: Fixed Status: Resolved (was: Ready to Commit) > Test failure: org.apache.cassandra.db.compaction.LongCompactionsTest > - > > Key: CASSANDRA-18884 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18884 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Stefan Miklosovic >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 5.0, 5.1 > > Time Spent: 40m > Remaining Estimate: 0h > > org.apache.cassandra.db.compaction.LongCompactionsTest in "long" tests is > broken. This seems to be a regression after CASSANDRA-18737 > If I checkout the code one merge before (CASSANDRA-18871), these tests do not > fail there. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-18884) Test failure: org.apache.cassandra.db.compaction.LongCompactionsTest
[ https://issues.apache.org/jira/browse/CASSANDRA-18884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacek Lewandowski updated CASSANDRA-18884: -- Status: Ready to Commit (was: Review In Progress) > Test failure: org.apache.cassandra.db.compaction.LongCompactionsTest > - > > Key: CASSANDRA-18884 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18884 > Project: Cassandra > Issue Type: Bug > Components: Test/unit >Reporter: Stefan Miklosovic >Assignee: Jacek Lewandowski >Priority: Normal > Fix For: 5.0.x, 5.x > > Time Spent: 40m > Remaining Estimate: 0h > > org.apache.cassandra.db.compaction.LongCompactionsTest in "long" tests is > broken. This seems to be a regression after CASSANDRA-18737 > If I checkout the code one merge before (CASSANDRA-18871), these tests do not > fail there. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch cassandra-5.0 updated (164fa7949d -> 6de90bf75c)
This is an automated email from the ASF dual-hosted git repository. jlewandowski pushed a change to branch cassandra-5.0 in repository https://gitbox.apache.org/repos/asf/cassandra.git from 164fa7949d Add support for repair coordinator to retry messages that timeout add 6de90bf75c Fix LongCompactionTest No new revisions were added by this update. Summary of changes: .../apache/cassandra/io/sstable/SSTableUtils.java | 26 +++--- 1 file changed, 8 insertions(+), 18 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-5.0' into trunk
This is an automated email from the ASF dual-hosted git repository. jlewandowski pushed a commit to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git commit d1158bfd8ea6b05e008c1af538ef622d3f2ae0d0 Merge: c96185f188 6de90bf75c Author: Jacek Lewandowski AuthorDate: Thu Sep 28 08:01:12 2023 +0200 Merge branch 'cassandra-5.0' into trunk * cassandra-5.0: Fix LongCompactionTest .../apache/cassandra/io/sstable/SSTableUtils.java | 26 +++--- 1 file changed, 8 insertions(+), 18 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[cassandra] branch trunk updated (c96185f188 -> d1158bfd8e)
This is an automated email from the ASF dual-hosted git repository. jlewandowski pushed a change to branch trunk in repository https://gitbox.apache.org/repos/asf/cassandra.git from c96185f188 Merge branch 'cassandra-5.0' into trunk add 6de90bf75c Fix LongCompactionTest new d1158bfd8e Merge branch 'cassandra-5.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: .../apache/cassandra/io/sstable/SSTableUtils.java | 26 +++--- 1 file changed, 8 insertions(+), 18 deletions(-) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
