Re: Cassandra CI Status 2023-01-07

[Dan Jatnieks]

New Failures from Build Lead Week 6:

*** CASSANDRA-18021 - Flaky
org.apache.cassandra.distributed.test.ReprepareTestOldBehaviour#testReprepareMixedVersionWithoutReset
- This existing ticket has been linked in butler to new failures on 3.11

*** CASSANDRA-17608 - Fix testMetricsWithRebuildAndStreamingToTwoNodes
- Re-opened as intermittent failure occurred in build 1445 on trunk

Several new failures had only a single occurrence; no new tickets were
opened during this time.



On Fri, Feb 10, 2023 at 12:44 AM Claude Warren, Jr via dev <
dev@cassandra.apache.org> wrote:

> New Failures from Build Lead Week 5
>
> *** CASSANDRA-18198 - "AttributeError: module 'py' has no attribute 'io'"
> reported in multiple tests
> - reported in 4.1, 3.11, and 3.0
> - identified as a possible class loader issue associated with
> CASSANDRA-18150
>
> *** CASSANDRA-18191 - Native Transport SSL tests failing
> - TestNativeTransportSSL.test_connect_to_ssl and
> TestNativeTransportSSL.test_connect_to_ssl (novnode)
> - TestNativeTransportSSL.test_connect_to_ssl_optional and
> TestNativeTransportSSL.test_connect_to_ssl_optional (nvnode)
>
>
> On Mon, Jan 23, 2023 at 10:10 PM Caleb Rackliffe 
> wrote:
>
>> New failures from Build Lead Week 4:
>>
>> *** CASSANDRA-18188 - Test failure in
>> upgrade_tests.cql_tests.cls.test_limit_ranges
>> - trunk
>> - AttributeError: module 'py' has no attribute 'io'
>>
>> *** CASSANDRA-18189 - Test failure in
>> cqlsh_tests.test_cqlsh_copy.TestCqlshCopy.test_bulk_round_trip_with_timeouts
>> - 4.0
>> - assert 10 == 94764
>> - other failures currently open in this test class, but at least
>> superficially, different errors (see CASSANDRA-17322, CASSANDRA-18162)
>>
>> Timeouts continue to manifest in many places.
>>
>> On Sun, Jan 15, 2023 at 6:02 AM Mick Semb Wever  wrote:
>>
>>> *** The Butler (Build Lead)

 The introduction of Butler and the Build Lead was a wonderful
 improvement to our CI efforts.  It has brought a lot of hygiene in
 listing out flakies as they happened.  Noted that this has in-turn
 increased the burden in getting our major releases out, but that's to
 be seen as a one-off cost.

>>>
>>>
>>> New Failures from Build Lead Week 3.
>>>
>>>
>>> *** CASSANDRA-18156
>>> – 
>>> repair_tests.deprecated_repair_test.TestDeprecatedRepairNotifications.test_deprecated_repair_error_notification
>>>  - AssertionError: Node logs don't have an error message for the failed
>>> repair
>>>  - hard regression
>>>  - 3.0, 3.11,
>>>
>>> *** CASSANDRA-18164 – CASTest Message serializedSize(12) does not match
>>> what was written with serialize(out, 12) for verb
>>> PAXOS2_COMMIT_AND_PREPARE_RSP
>>>  - serializer class org.apache.cassandra.net.Message$Serializer;
>>> expected 1077, actual 1079
>>>  - 4.1, trunk
>>>
>>> *** CASSANDRA-18158
>>> – 
>>> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck
>>>  - Cannot achieve consistency level ALL
>>>  - 3.11, trunk
>>>
>>> *** CASSANDRA-18159 – repair_tests.repair_test.TestRepair.test_*dc_repair
>>>   - AssertionError: null
>>> in MemtablePool$SubPool.released(MemtablePool.java:193)
>>>  - 3.11, 4.0, 4.1, trunk
>>>
>>> *** CASSANDRA-18160
>>> – 
>>> cdc_test.TestCDC.test_insertion_and_commitlog_behavior_after_reaching_cdc_total_space
>>>  - Found orphaned index file in after CDC state not in former
>>>  - 4.1, trunk
>>>
>>> *** CASSANDRA-18161 –
>>>  
>>> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame
>>>  - AssertionFailedError in
>>> CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:491)
>>>  - 4.0, 4.1, trunk
>>>
>>> *** CASSANDRA-18162 –
>>> cqlsh_tests.test_cqlsh_copy.TestCqlshCopy.test_bulk_round_trip_non_prepared_statements
>>> - Inet address 127.0.0.3:7000
>>> 
>>> is not available: [Errno 98] Address already in use
>>> - 3.0, 3.11, 4.0, 4.1, trunk
>>>
>>> *** CASSANDRA-18163 –
>>>  
>>> transient_replication_test.TestTransientReplicationRepairLegacyStreaming.test_speculative_write_repair_cycle
>>>  - AssertionError Incoming stream entireSSTable
>>>  - 4.0, 4.1, trunk
>>>
>>>
>>> While writing these up, some thoughts…
>>>  - While Butler reports failures against multiple branches, there's no
>>> feedback/sync that the ticket needs its fixVersions updated when failures
>>> happen in other branches after the ticket is created.
>>>  - In 4.0 onwards, a majority of the failures are timeouts (>900s),
>>> reinforcing that the current main problem we are facing in ci-cassandra.a.o
>>> is saturation/infra
>>>
>>>
>>>
>>>
>>>

Re: [VOTE] CEP-21 Transactional Cluster Metadata

[Jeremy Hanna]

I just want to say after Alex's presentation at ApacheCon, I'm really excited 
about this as an underappreciated feature for 5.0: how it will help cluster 
stability through membership changes and schema evolutions, how it will improve 
both the scalability of clusters and the flexibility of replica placement, and 
some interesting possibilities once this foundation is in place.  For any 
interested, Alex's talk was recorded and is found here: 
https://drive.google.com/file/d/1LKNpp3rnBlHnls3HUMRZAL9W1llylN0a/view?usp=sharing

> On Feb 10, 2023, at 2:46 AM, Sam Tunnicliffe  wrote:
> 
> The vote passes with 23 +1s (13 binding) and no negative votes.
> 
> Thanks all,
> Sam
> 
> 
>> On 6 Feb 2023, at 16:15, Sam Tunnicliffe  wrote:
>> 
>> Hi everyone,
>> 
>> I would like to start a vote on this CEP.
>> 
>> Proposal:
>> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21%3A+Transactional+Cluster+Metadata
>> 
>> Discussion:
>> https://lists.apache.org/thread/h25skwkbdztz9hj2pxtgh39rnjfzckk7
>> 
>> The vote will be open for 72 hours.
>> A vote passes if there are at least three binding +1s and no binding vetoes.
>> 
>> Thanks,
>> Sam
> 

Re: [VOTE] CEP-21 Transactional Cluster Metadata

[Sam Tunnicliffe]

The vote passes with 23 +1s (13 binding) and no negative votes.

Thanks all,
Sam


> On 6 Feb 2023, at 16:15, Sam Tunnicliffe  wrote:
> 
> Hi everyone,
> 
> I would like to start a vote on this CEP.
> 
> Proposal:
> https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21%3A+Transactional+Cluster+Metadata
> 
> Discussion:
> https://lists.apache.org/thread/h25skwkbdztz9hj2pxtgh39rnjfzckk7
> 
> The vote will be open for 72 hours.
> A vote passes if there are at least three binding +1s and no binding vetoes.
> 
> Thanks,
> Sam

Re: Cassandra CI Status 2023-01-07

[Claude Warren, Jr via dev]

New Failures from Build Lead Week 5

*** CASSANDRA-18198 - "AttributeError: module 'py' has no attribute 'io'"
reported in multiple tests
- reported in 4.1, 3.11, and 3.0
- identified as a possible class loader issue associated with
CASSANDRA-18150

*** CASSANDRA-18191 - Native Transport SSL tests failing
- TestNativeTransportSSL.test_connect_to_ssl and
TestNativeTransportSSL.test_connect_to_ssl (novnode)
- TestNativeTransportSSL.test_connect_to_ssl_optional and
TestNativeTransportSSL.test_connect_to_ssl_optional (nvnode)


On Mon, Jan 23, 2023 at 10:10 PM Caleb Rackliffe 
wrote:

> New failures from Build Lead Week 4:
>
> *** CASSANDRA-18188 - Test failure in
> upgrade_tests.cql_tests.cls.test_limit_ranges
> - trunk
> - AttributeError: module 'py' has no attribute 'io'
>
> *** CASSANDRA-18189 - Test failure in
> cqlsh_tests.test_cqlsh_copy.TestCqlshCopy.test_bulk_round_trip_with_timeouts
> - 4.0
> - assert 10 == 94764
> - other failures currently open in this test class, but at least
> superficially, different errors (see CASSANDRA-17322, CASSANDRA-18162)
>
> Timeouts continue to manifest in many places.
>
> On Sun, Jan 15, 2023 at 6:02 AM Mick Semb Wever  wrote:
>
>> *** The Butler (Build Lead)
>>>
>>> The introduction of Butler and the Build Lead was a wonderful
>>> improvement to our CI efforts.  It has brought a lot of hygiene in
>>> listing out flakies as they happened.  Noted that this has in-turn
>>> increased the burden in getting our major releases out, but that's to
>>> be seen as a one-off cost.
>>>
>>
>>
>> New Failures from Build Lead Week 3.
>>
>>
>> *** CASSANDRA-18156
>> – 
>> repair_tests.deprecated_repair_test.TestDeprecatedRepairNotifications.test_deprecated_repair_error_notification
>>  - AssertionError: Node logs don't have an error message for the failed
>> repair
>>  - hard regression
>>  - 3.0, 3.11,
>>
>> *** CASSANDRA-18164 – CASTest Message serializedSize(12) does not match
>> what was written with serialize(out, 12) for verb
>> PAXOS2_COMMIT_AND_PREPARE_RSP
>>  - serializer class org.apache.cassandra.net.Message$Serializer;
>> expected 1077, actual 1079
>>  - 4.1, trunk
>>
>> *** CASSANDRA-18158
>> – 
>> org.apache.cassandra.distributed.upgrade.MixedModeReadTest.mixedModeReadColumnSubsetDigestCheck
>>  - Cannot achieve consistency level ALL
>>  - 3.11, trunk
>>
>> *** CASSANDRA-18159 – repair_tests.repair_test.TestRepair.test_*dc_repair
>>   - AssertionError: null
>> in MemtablePool$SubPool.released(MemtablePool.java:193)
>>  - 3.11, 4.0, 4.1, trunk
>>
>> *** CASSANDRA-18160
>> – 
>> cdc_test.TestCDC.test_insertion_and_commitlog_behavior_after_reaching_cdc_total_space
>>  - Found orphaned index file in after CDC state not in former
>>  - 4.1, trunk
>>
>> *** CASSANDRA-18161 –
>>  
>> org.apache.cassandra.transport.CQLConnectionTest.handleCorruptionOfLargeMessageFrame
>>  - AssertionFailedError in
>> CQLConnectionTest.testFrameCorruption(CQLConnectionTest.java:491)
>>  - 4.0, 4.1, trunk
>>
>> *** CASSANDRA-18162 –
>> cqlsh_tests.test_cqlsh_copy.TestCqlshCopy.test_bulk_round_trip_non_prepared_statements
>> - Inet address 127.0.0.3:7000 is not available: [Errno 98] Address
>> already in use
>> - 3.0, 3.11, 4.0, 4.1, trunk
>>
>> *** CASSANDRA-18163 –
>>  
>> transient_replication_test.TestTransientReplicationRepairLegacyStreaming.test_speculative_write_repair_cycle
>>  - AssertionError Incoming stream entireSSTable
>>  - 4.0, 4.1, trunk
>>
>>
>> While writing these up, some thoughts…
>>  - While Butler reports failures against multiple branches, there's no
>> feedback/sync that the ticket needs its fixVersions updated when failures
>> happen in other branches after the ticket is created.
>>  - In 4.0 onwards, a majority of the failures are timeouts (>900s),
>> reinforcing that the current main problem we are facing in ci-cassandra.a.o
>> is saturation/infra
>>
>>
>>
>>
>>

Re: [VOTE] Release Apache Cassandra 4.0.8

[Tommy Stendahl via dev]

+1 (nb)

-Original Message-
From: Berenguer Blasi 
mailto:berenguer%20blasi%20%3cberenguerbl...@gmail.com%3e>>
Reply-To: dev@cassandra.apache.org
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release Apache Cassandra 4.0.8
Date: Thu, 09 Feb 2023 13:49:01 +0100


+1


On 9/2/23 12:50, Brandon Williams wrote:

+1


Kind Regards,

Brandon


On Thu, Feb 9, 2023 at 4:56 AM Miklosovic, Stefan

<



stefan.mikloso...@netapp.com

> wrote:

Proposing the test build of Cassandra 4.0.8 for release.


sha1: 32c56df067b72da8593c1ddaaf143fe8668459dd

Git:



https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.0.8-tentative


Maven Artifacts:



https://repository.apache.org/content/repositories/orgapachecassandra-1283/org/apache/cassandra/cassandra-all/4.0.8/



The Source and Build Artifacts, and the Debian and RPM packages and 
repositories, are available here:



https://dist.apache.org/repos/dist/dev/cassandra/4.0.8/



The vote will be open for 72 hours (longer if needed). Everyone who has tested 
the build is invited to vote. Votes by PMC members are considered binding. A 
vote passes if there are at least three binding +1s and no -1's.


[1]: CHANGES.txt:



https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.0.8-tentative


[2]: NEWS.txt:



https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.0.8-tentative