[
https://issues.apache.org/jira/browse/RANGER-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fateh Singh updated RANGER-5205:
--------------------------------
Description:
*Current flow for upgrade:*
# Take database backup
# Stop services (ranger/kms)
# Upgrade ranger database by applying schema changes and java patches
# Upgrade the bits with new version and restart the services.
If now something goes wrong after the upgrade after some time of running the
services, the user now has to restore the database from the backup before
upgrade before restoring the old bits and restarting the services.
*Key limitations in the current framework for db upgrade:*
# Leads to downtime
# Can lead to loss of data if need for downgrade arises
*How Liquibase helps:*
# Provides a construct of rollback natively which can help developers write
backward compatible db schema changes and java patches which can prevent
downtime
# Will allow to downgrade without restoring the db hence preventing data loss
*Design document and architecture:*
[https://docs.google.com/document/d/1kDbrdN9n2yNzmkwwDd_Gx90jxN3VxTfTKvMKEJiplG0/edit?tab=t.0]
was:
*Current flow for upgrade:*
# Take database backup
# Stop services (ranger/kms)
# Upgrade ranger database by applying schema changes and java patches
# Upgrade the bits with new version and restart the services.
If now something goes wrong after the upgrade after some time of running the
services, the user now has to restore the database from the backup before
upgrade before restoring the old bits and restarting the services.
*Key limitations in the current framework for db upgrade:*
# Leads to downtime
# Can lead to loss of data if need for downgrade arises
*How Liquibase helps:*
# Provides a construct of rollback natively which can help developers write
backward compatible db schema changes and java patches which can prevent
downtime
# Will allow to downgrade without restoring the db hence preventing data loss
> Liquibase based Zero-Downtime-Upgrade framework for Ranger
> ----------------------------------------------------------
>
> Key: RANGER-5205
> URL: https://issues.apache.org/jira/browse/RANGER-5205
> Project: Ranger
> Issue Type: New Feature
> Components: kms, Ranger
> Reporter: Fateh Singh
> Assignee: Fateh Singh
> Priority: Major
>
> *Current flow for upgrade:*
> # Take database backup
> # Stop services (ranger/kms)
> # Upgrade ranger database by applying schema changes and java patches
> # Upgrade the bits with new version and restart the services.
> If now something goes wrong after the upgrade after some time of running the
> services, the user now has to restore the database from the backup before
> upgrade before restoring the old bits and restarting the services.
> *Key limitations in the current framework for db upgrade:*
> # Leads to downtime
> # Can lead to loss of data if need for downgrade arises
> *How Liquibase helps:*
> # Provides a construct of rollback natively which can help developers write
> backward compatible db schema changes and java patches which can prevent
> downtime
> # Will allow to downgrade without restoring the db hence preventing data
> loss
> *Design document and architecture:*
> [https://docs.google.com/document/d/1kDbrdN9n2yNzmkwwDd_Gx90jxN3VxTfTKvMKEJiplG0/edit?tab=t.0]
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
