You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

References

CPS-438 - Getting issue details... STATUS

Background

Liquibase container attempts restart if it takes too long. Liquibase does not release the changelog lock on the data table if it gets restarted. An init container should be used which will not restart and will run until completion.

Possible Fixes:

FixNameDescriptionCost/MaintainabilityAgnostic of database technologySeparation of NCMP Data

Upgradability/

Rollback

Additional Pros/Cons
1Liquibase init container
  1. Add init container to oom
    1. Restart issues are only happening with kubernetes restarting liquibase
  2. Add "depends on" container to cps
    1. cps standalone deployment is not effected by kubernetes issue
  1. Double changelog dependency? one in oom, one in cps
  2. Changes to oom and cps projects
Yes including Neo4JIs possible but needs some refactoring (Labeling)GoodGood control of database versioning
2Change/Add liveness probes?Liquibase container is restarted by Kubernetes as it does not read a readiness probe within a certain amount of time. We could extend the time limit, change the restart condition etc...
  1. Timing updates
No changeNo changeGood
3Remove Liquibase and replace with similar technologyReplace Liquibase with Flyway
  1. Migrate from Liquibase 
  2. Flyway only does sql changelogs, would have to change from yaml > sql

Flyway does not support NoSQL: Neo4J

PossibleGood

Would solve  CPS-963 - Getting issue details... STATUS

Might come with same issue as Liquibase as is more of a Kubernetes issue?

4

Use cps-core API

Trigger code/script triggered by springboot that will persist the required data
  1. Migrate from Liquibase 
Yes including Neo4JEasyRequires some code

Would solve  CPS-963 - Getting issue details... STATUS

Do we need database migration technologies? Rollback etc

5Use Session lock instead of transaction lock for Liquibase

https://mvnrepository.com/artifact/com.github.blagerweij/liquibase-sessionlock/1.2.5

Changeloglock will be dropped once session is dropped by Liquibase container

  1. No change
Yes including Neo4JIs possible but needs some refactoring (Labeling)Good
  1. Depends on privately owned 3pp
  2. Doesn't stop kubernetes from restarting the container, just makes it so that the changeloglock will not be retained. 
6Execute Liquibase logic in Spring Boot Service Start Up

Solution 3: https://localcoder.org/how-to-solve-liquibase-waiting-for-changelog-lock-problem-in-several-pods-in-ope

https://docs.spring.io/spring-boot/docs/current/reference/html/howto.html#howto.data-initialization.migration-tool.liquibase

Liquibase start up is contained within CPS start up so can avoid kubernetes Liquibase setup

  1. Change to how Liquibase is started
Yes including Neo4JIs possible but needs some refactoring (Labeling)Good

Springboot supported solution

  • No labels