[
https://issues.apache.org/jira/browse/GEODE-3316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16155800#comment-16155800
]
ASF subversion and git services commented on GEODE-3316:
--------------------------------------------------------
Commit 841d4e9031d3336c6c4d4f541088a46ddd7faae2 in geode's branch
refs/heads/develop from [~barry.oglesby]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=841d4e9 ]
GEODE-3316: Modified tests to roll locator and server
> Fix the order of rolling members in RollingUpgrade related tests
> ----------------------------------------------------------------
>
> Key: GEODE-3316
> URL: https://issues.apache.org/jira/browse/GEODE-3316
> Project: Geode
> Issue Type: Bug
> Components: tests
> Reporter: nabarun
> Assignee: nabarun
>
> In test classes like RollingUpgrade2DUnit and WANRollingUpgrade, there are
> tests with clusters which have new version servers connected to an older
> version locator.
> These tests should be refactored so that everything starts at an older
> version, then follows the following order of upgrade.
> 1. Locators are rolled first to the current version
> 2. Then the servers are upgraded to current version
> 3. And at last the clients are upgraded.
> Queries/ data verification must done in between these steps to confirm that
> the data integrity is maintained while upgrades are happening
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
