[ 
https://issues.apache.org/jira/browse/CASSANDRA-20536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Semb Wever updated CASSANDRA-20536:
-------------------------------------------
    Description: 
cassandra-dtests perform upgrade tests
for example, see 
https://github.com/apache/cassandra-dtest/tree/trunk/upgrade_tests

The ccm tool should be able to support this same capability for upgrades across 
different cluster types ( ref CASSANDRA-20456 ).

This patch fixes/improves a few low-level aspects of 20456 to make such 
mix-type upgrades possible.

Specifically, these are
 - the cluster and node handling of determining the cassandra version from 
build directories,
 - the ability to switch between JAVAx_HOME configured jdks, and
 - failure handling and error messaging around the use of generatetokens.

Patches: 
- 
https://github.com/apache/cassandra-ccm/compare/trunk...thelastpickle:cassandra-ccm:mck/upgrade-tests-fixes
- https://github.com/apache/cassandra-dtest/pull/275 

  was:
cassandra-dtests perform upgrade tests
for example, see 
https://github.com/apache/cassandra-dtest/tree/trunk/upgrade_tests

The ccm tool should be able to support this same capability for upgrades across 
different cluster types ( ref CASSANDRA-20456 ).

This patch fixes/improves a few low-level aspects of 20456 to make such 
mix-type upgrades possible.

Specifically, these are
 - the cluster and node handling of determining the cassandra version from 
build directories,
 - the ability to switch between JAVAx_HOME configured jdks, and
 - failure handling and error messaging around the use of generatetokens.

Patch: 
https://github.com/apache/cassandra-ccm/compare/trunk...thelastpickle:cassandra-ccm:mck/upgrade-tests-fixes


> CCM improved support for upgrade tests between different cluster types
> ----------------------------------------------------------------------
>
>                 Key: CASSANDRA-20536
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-20536
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Tool/CCM
>            Reporter: Michael Semb Wever
>            Assignee: Michael Semb Wever
>            Priority: Normal
>              Labels: pull-request-available
>         Attachments: 
> ci_summary_ccm_thelastpickle_mck-upgrade-tests-fixes_205.html, 
> results_details_ccm_thelastpickle_mck-upgrade-tests-fixes_205.tar.xz
>
>
> cassandra-dtests perform upgrade tests
> for example, see 
> https://github.com/apache/cassandra-dtest/tree/trunk/upgrade_tests
> The ccm tool should be able to support this same capability for upgrades 
> across different cluster types ( ref CASSANDRA-20456 ).
> This patch fixes/improves a few low-level aspects of 20456 to make such 
> mix-type upgrades possible.
> Specifically, these are
>  - the cluster and node handling of determining the cassandra version from 
> build directories,
>  - the ability to switch between JAVAx_HOME configured jdks, and
>  - failure handling and error messaging around the use of generatetokens.
> Patches: 
> - 
> https://github.com/apache/cassandra-ccm/compare/trunk...thelastpickle:cassandra-ccm:mck/upgrade-tests-fixes
> - https://github.com/apache/cassandra-dtest/pull/275 



--
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

Reply via email to