fix(instance,scaleup): avoid using snapshots if they could be of an older majorVersion#8475
fix(instance,scaleup): avoid using snapshots if they could be of an older majorVersion#8475gbartolini merged 5 commits intomainfrom
Conversation
|
❗ By default, the pull request is configured to backport to all release branches.
|
26c394e to
1633d59
Compare
3fe9c49 to
39c3bc1
Compare
c7262b6 to
19b92bc
Compare
a053ec0 to
8ded6ac
Compare
bdb555f to
0cacf2d
Compare
39cf270 to
014c550
Compare
0cacf2d to
5650cbd
Compare
80a26c0 to
6415086
Compare
3677c35 to
5e75152
Compare
|
/test |
|
@mnencia, here's the link to the E2E on CNPG workflow run: https://github.com/cloudnative-pg/cloudnative-pg/actions/runs/17673850865 |
…lder majorVersion Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> wip Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> test: add tests Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
1146110 to
ed5a36c
Compare
… upgrades (#8475) Avoids a bug where volume snapshot backups from a previous minor version could be incorrectly reused when scaling up, leading to issues during major PostgreSQL upgrades. Depends On #8464 Closes #7705 Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 62c6bd0)
… upgrades (#8475) Avoids a bug where volume snapshot backups from a previous minor version could be incorrectly reused when scaling up, leading to issues during major PostgreSQL upgrades. Depends On #8464 Closes #7705 Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> (cherry picked from commit 62c6bd0)
… upgrades (cloudnative-pg#8475) Avoids a bug where volume snapshot backups from a previous minor version could be incorrectly reused when scaling up, leading to issues during major PostgreSQL upgrades. Depends On cloudnative-pg#8464 Closes cloudnative-pg#7705 Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
|
Apologies for waking this up - however we've just begun testing and hit the issue where this ticket is attempting to fix. However, I don't think the fix here is sufficient specially for large databases. When creating replicas it decides how to do it in following code: where This default method won't work because of database sizes. Proper way of doing it would be to take backup of primary after upgrade using snapshot method and only then create replica, but it doesn't seem to do it. So for big enough instances we'll need to have custom upgrade procedure regardless of CNPG version:
I believe the custom upgrade procedure described above should be the proper fix. Does this make sense? |
… upgrades (cloudnative-pg#8475) Avoids a bug where volume snapshot backups from a previous minor version could be incorrectly reused when scaling up, leading to issues during major PostgreSQL upgrades. Depends On cloudnative-pg#8464 Closes cloudnative-pg#7705 Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com> Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Co-authored-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com> Signed-off-by: theBrahma <office.utpal.brahma@gmail.com>
Fixes a bug during major upgrades where a volume snapshot backup from a previous minor version could have been incorrectly used to optimise the recreation of replicas.
Depends On #8464
Closes #7705