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

Michael Semb Wever edited comment on CASSANDRA-18106 at 3/2/23 12:54 PM:
-------------------------------------------------------------------------

Gotcha, _python upgrade dtest upgrade_ that are upgrading the jvm during the 
test… TIL.

Are there really any tests that switch the jdk during the test…? and if so, why 
any longer? 
A quick search and I cannot find any such tests, and my vote is on not 
recommending to users (or supporting) switch C* versions and JDK version on the 
same node restart (Operators should be de-risking by default).


was (Author: michaelsembwever):
Gotcha, python dtest upgrade tests, that are upgrading the jvm during the test… 
TIL.

Are there really any tests that switch the jdk during the test…? and if so, why 
any longer? 
A quick search and I cannot find any such tests, and my vote is on not 
recommending to users (or supporting) switch C* versions and JDK version on the 
same node restart (Operators should be de-risking by default).

> Update CCM for JDK17 and revise current JDK detection strategy
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-18106
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18106
>             Project: Cassandra
>          Issue Type: Task
>          Components: CI
>            Reporter: Ekaterina Dimitrova
>            Assignee: Brandon Williams
>            Priority: Normal
>             Fix For: 4.x
>
>
> As part of CASSANDRA-16895 initial POC an initial version of CCM patch was 
> created. This needs to be revisited and reviewed
> Recently we closed CASSANDRA-18039 which brought questions, probably we need 
> to revise how we detect JDK versions in CCM and whether it is correct. To the 
> best of my knowledge there are certain tests in the repo around that and they 
> pass so my guess is we need to revise just the strategy and maybe document it 
> explicitly or consider if we want any changes to be applied. Also, we need to 
> be careful with breaking changes. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to