You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Aleksandr Chesnokov (Jira)" <ji...@apache.org> on 2026/08/28 12:34:00 UTC
[jira] [Updated] (IGNITE-28982) Enable real Rolling Upgrade mode in testcontainers compatibility tests
[ https://issues.apache.org/jira/browse/IGNITE-28982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aleksandr Chesnokov updated IGNITE-28982:
-----------------------------------------
Labels: ise (was: )
> Enable real Rolling Upgrade mode in testcontainers compatibility tests
> ----------------------------------------------------------------------
>
> Key: IGNITE-28982
> URL: https://issues.apache.org/jira/browse/IGNITE-28982
> Project: Ignite
> Issue Type: Bug
> Reporter: Aleksandr Chesnokov
> Assignee: Aleksandr Chesnokov
> Priority: Major
> Labels: ise
> Time Spent: 40m
> Remaining Estimate: 0h
>
> For now compatibility testcontainers use DisabledRollingUpgradeProcessor, which has naive implementation
>
> {code:java}
> @Nullable @Override public IgniteNodeValidationResult validateNode(ClusterNode node) {
> return null;
> } {code}
> Problem is that real processor has sophisticated logic for validation and it is not tested in testcontainers
>
> Let's implement provider that gives real RollingUpgradeProcessor but enabled by default. Probably it will be called AutoEnabledRollingUpgradeProcessor
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)