ChangeSet applied twice about liquibase-sessionlock HOT 2 CLOSED

This seems like a problem in Liquibase itself (not the lock implementation). You'll notice these lines in pod #3:
INFO 2023-08-29T11:06:10.703Z Successfully acquired change log lock
INFO 2023-08-29T11:06:13.105Z Reading from rfid.DATABASECHANGELOG
INFO 2023-08-29T11:06:13.382Z Successfully released change log lock
At this time, the second pod has not finished, so the DATABASECHANGELOG will not have the changeset marked as done.
Then later, after it acquired the lock again, it will execute the changesets which it think still need execution, but it does not reread from the DATABASECHANGELOG table.

Either Liquibase should not release the lock between the read and execute, or it should reread from the DATABASECHANGELOG table. Are you able to upgrade to the latest version of Liquibase, to see if the problem is still present in the latest version?

It would be nice to include an integration test for your scenario, but I also realize it might be hard to implement.

from liquibase-sessionlock.

Thank you for your answer, after some more testing, debugging and digging through Liquibase release notes, I think I found why the lock is released after readnig the rfid.DATABASECHANGELOG table: Liquibase Issue.

For some reason without liquibase-sessionlock the change set was never applied twice in my tests, but with it it was always applied twice.

The releasing of the lock was fixed in Liquibase v4.4.1, so I upgraded our Spring Boot version to 2.7.15 which uses Liquibase version 4.9.1, and ran my tests again, the lock was not released between reading the rfid.DATABASECHANGELOG table and applying the change set, with or without liquibase-sessionlock.

It was just a coincidence, that after adding the liquibase-sessionlock dependency I started to notice the change set applying twice.

Thank you again for your answer, I'll close this issue.

from liquibase-sessionlock.