0

I have a SpringBoot application that will fail to start up when the database it is using is not up since the datasource bean will fail to initialize. I want for my application to not start before my db is up in order to avoid this failure.

To mention that this app is running in Kubernetes so one option would be to use an init-container. I would want though to have that logic inside the application itself.

First of all, is that a bad idea and I should stick with init-containers?

If it is not a bad idea what is usually the best approach for this. I was looking at Spring Retry and one possible solution seems to be to have retry logic in the @Bean datasource initialization method. Does that have any possible drawbacks? Is there a better way?

dragosb
  • 607
  • 8
  • 25
  • 1
    Please check out this link https://deinum.biz/2020-06-30-Wait-for-database-startup/ – Simon Martinelli Oct 21 '20 at 12:47
  • Maybe I am missing something, but there it seems that the datasource object needs to be created for it to work. My problem is that my datasource bean fails on creation because it needs to connect to the db. – dragosb Oct 21 '20 at 13:08

2 Answers2

0

Not sure if this works for you but in case you have Data source beans declared.

You can you @Lazy annotation to delay the bean initialization until required.

Your application startup shouldn't fail on startup as the Datasource bean would not be initialized until needed

Ayush v
  • 351
  • 2
  • 9
  • 1
    Not a bad suggestion. But if the application starts up and gets requests before db is ready then I would still get an error. – dragosb Oct 21 '20 at 14:45
  • Maybe a work around could be change the application logic to not initialize the datasource bean until Db is up. Although this statement seems to be a bit vaug though – Ayush v Oct 21 '20 at 14:52
0

You can have a startup probe to check DB connections at the start. If you want the DB connections to be constantly pooled for health, you can use other probles. Or in the pipeline which you use to deploy, after the check build unittest phases, you can add a step to check connections of external services/db which you use.

Patrick
  • 1,635
  • 2
  • 13
  • 23