[
https://issues.apache.org/jira/browse/CASSANDRA-18345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17738769#comment-17738769
]
Ekaterina Dimitrova edited comment on CASSANDRA-18345 at 6/29/23 8:23 PM:
--------------------------------------------------------------------------
Happy to see people consider the JDK17 experimental CircleCI config. (Jenkins
runs only the test suites that are already fixed, but we can run all tests and
see the failures in CircleCI)
List of failures we are still seeing is regularly updated in the description of
CASSANDRA-16895.
Last update:
|| ||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|
| |_Burn tests_| |
|1|org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression|CASSANDRA-18570|
I keep on updating it. regularly.
was (Author: e.dimitrova):
Happy to see people consider the JDK17 experimental CircleCI config. (Jenkins
runs only the test suites that are already fixed)
List of failures we are still seeing is regularly updated in the description of
CASSANDRA-16895.
Last update:
|| ||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|
| |_Burn tests_| |
|1|org.apache.cassandra.transport.DriverBurnTest.measureLargeV4WithCompression|CASSANDRA-18570|
I keep on updating it. regularly.
> Enable streaming SAI components as part of repair
> -------------------------------------------------
>
> Key: CASSANDRA-18345
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18345
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/2i Index
> Reporter: Mike Adamson
> Assignee: Piotr Kolaczkowski
> Priority: Normal
> Labels: SAI
> Fix For: 5.x
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> SAI registers it's components with the SSTable descriptor expecting them to
> form part of the SSTable lifecycle, including streaming. This is not the case.
> The current SSTable format in Cassandra uses a fixed set of components
> (Components.STREAMING_COMPONENTS) when streaming SSTables. This needs to
> change to use the set of components that are registered with a specific
> SSTable by calls to SSTable.registerComponents.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
