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

Possible race condition on MetaDataTable-Upgrade #1368

Closed
shadev opened this issue Jul 18, 2016 · 0 comments
Closed

Possible race condition on MetaDataTable-Upgrade #1368

shadev opened this issue Jul 18, 2016 · 0 comments

Comments

@shadev
Copy link

shadev commented Jul 18, 2016

What version of Flyway are you using?

4.0.3

What database are you using (type & version)?

Oracle 11g

What operating system are you using?

CentOS

What did you do?

Upgrade from Flyway 3.2.1 to 4.0.3 in an multi-node environment (sharing the same DB). Flyway-Migrate is triggered via Spring on SpringContext-Initialization.

What did you expect to see?

MetaDataTable-Upgrade performed successfully

What did you see instead?

MetaDataTable-Upgrade started on multiple nodes in parallel conflicting with each other.

I think the code is missing an MetaDataTable.lock() call in MetaDataTable.upgradeIfNecessary() like "normal" DB-Migrations

@axelfontaine axelfontaine added this to the Flyway 4.1 milestone Jul 18, 2016
axelfontaine pushed a commit to flyway/flywaydb.org that referenced this issue Feb 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants