Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Introduce connectRetries setting #2124

Closed
axelfontaine opened this issue Aug 29, 2018 · 2 comments
Closed

Introduce connectRetries setting #2124

axelfontaine opened this issue Aug 29, 2018 · 2 comments
Labels
m: Core r: fixed t: feature
Milestone
Flyway 5.2.0

Comments

@axelfontaine
Copy link
Contributor

See flyway/flyway-docker#2 (comment)

Currently Flyway automatically tries to connect up to 10 times at a 1 second interval. This should be made configurable to deal with a number of use cases including Docker Compose where both the Flyway and the DB container are started at the same time and Flyway must wait for the DB container to come up before being able to migrate the database..
@axelfontaine axelfontaine added this to the Flyway 5.2.0 milestone Aug 29, 2018
@axelfontaine axelfontaine changed the title Introduce connectTimeout setting Introduce connectRetries setting Sep 20, 2018
axelfontaine pushed a commit to flyway/flywaydb.org that referenced this issue Sep 20, 2018
Added notes for flyway/flyway#2124
d03bc7f
@AlexBoothClearswift
Copy link

Is the interval configurable to a value larger than 1 second?

@axelfontaine
Copy link
Contributor Author

@AlexBoothClearswift No. Please file a new feature request detailing your use case in detail and why the current approach doesn't work for you.

dohrayme pushed a commit to dohrayme/flyway that referenced this issue Feb 3, 2020
Fixed flyway#2124: Introduce connectRetries setting
c4eaef4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
m: Core r: fixed t: feature
Projects
None yet
Milestone
Flyway 5.2.0
Development

No branches or pull requests
2 participants
@axelfontaine @AlexBoothClearswift