[ 
https://issues.apache.org/jira/browse/CASSANDRA-17132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17442447#comment-17442447
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17132:
-------------------------------------------------

I reran the java 11 python no-vnodes DTests as they were failing with 
"UnavailableSocketError", typical when lacking CircleCI resources but just in 
case!
[This|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1188/workflows/8b8d24bc-b24e-439a-92e3-d6f4541ef9fb/jobs/7143/tests]
 is the new run which confirms my theory and doesn't show any new issues except 
the one failure which fix is about to be merged later today.


There are already tickets opened for - {_}test_speculative_data_request - 
read_repair_test.TestSpeculativeReadRepair{_}, I opened CASSANDRA-17139 for 
{_}org.apache.cassandra.distributed.test.ring.BootstrapTest{_}. There are 
already tickets for the python _upgrade dtests, 
testNoTreesRetainedAfterDifference, replaceAliveHost - 
org.apache.cassandra.distributed.test.hostreplacement.HostReplacementTest, 
utests_system_keyspace_directory_ tests


Different bootstrap tests are failing, it seems to me bootstrapping is unstable 
lately. I am wondering whether not to open an umbrella ticket. What do you 
think?
CompactStorage tests OOM from time to time. That seems more like CircleCI 
config needs to be polished? [~benedict], [~dcapwell], anyone of you up for a 
review?

> Fix startup issue with internode_application_timeout_in_ms
> ----------------------------------------------------------
>
>                 Key: CASSANDRA-17132
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17132
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Build
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Normal
>             Fix For: 4.0.x, 4.x
>
>
> While testing my patch for CASSANDRA-17131 I found that there is a problem 
> with _internode_application_timeout_in_ms_ in 4.0 and trunk.
> Seems to me that we can just safely remove it for now?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to