Closed Harduim closed 2 months ago
Hello @Harduim
Could you try to remove this part from your JDBC URL: ;DefaultKeyspace=KEYSPACE_NAME;AuthMech=1;
?
This is related to the Simba driver used until 4.24 and it's useless for ING Cassandra driver used since 4.25. Moreover, as it directly follows the compliancemode
parameter, this probably leads to misinterpeting this one and not running with the appropriate behaviour.
Not sure this solves your issue but it clearly might cause other ones.
Hi @maximevw, thanks for pointing that out!
Unfortunately changing the url to jdbc:cassandra://CASSANDRA_HOST:9042/KEYSPACE_NAME?localdatacenter=localdatacenter&compliancemode=Liquibase;
didn't make any difference.
This is the log output after the change:
[2024-04-07 22:16:41] FINE [liquibase.command] Executing internal command changeExecListener
[2024-04-07 22:16:41] FINE [liquibase.command] Executing internal command update
[2024-04-07 22:16:41] FINE [liquibase.configuration] No configuration value for liquibase.changelogLockWaitTimeInMinutes aka liquibase.changeLogLockWaitTimeInMinutes found
[2024-04-07 22:16:41] FINE [liquibase.configuration] Configuration liquibase.changelogLockWaitTimeInMinutes is using the default value of 5
[2024-04-07 22:16:41] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:16:41] FINE [liquibase.executor] Lock Database
[2024-04-07 22:16:41] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:16:41] FINE [liquibase.configuration] No configuration value for liquibase.changelogLockPollRate aka liquibase.changeLogLockPollRate found
[2024-04-07 22:16:41] FINE [liquibase.configuration] Configuration liquibase.changelogLockPollRate is using the default value of 10
[2024-04-07 22:16:52] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:16:52] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:17:02] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:17:03] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:17:13] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:17:13] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:17:24] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:17:24] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:17:34] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:17:34] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:17:45] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:17:45] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:17:55] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:17:56] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:18:06] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:18:06] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:18:17] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:18:17] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:18:27] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:18:28] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:18:38] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:18:38] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:18:49] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:18:49] INFO [liquibase.ext] Waiting for changelog lock....
[2024-04-07 22:18:59] FINE [liquibase.executor] Changelog query completed.
[2024-04-07 22:19:00] INFO [liquibase.ext] Waiting for changelog lock....
Here is the content of the databasechangeloglock during the wait.
id | locked | lockedby | lockgranted |
---|---|---|---|
1 | true | ideiapadg3 (****) | 2024-04-07 22:16:41.000 |
Thanks for your help.
@Harduim,
You must also remove the semicolon after Liquibase
. The parameter separator is &
for ING driver and consequently, here it tries to apply an unexistant Liquibase;
compliance mode and so fallbacks to the default driver behaviour causing known issues when running in Liquibase.
The error message is very similar to issue #249 but the cause is certainly different here. 🤔
@maximevw thanks for the help, that worked!
This log sequence suggests an issue where a Liquibase operation is trying to acquire a changelog lock but is unable to do so, leading to repeated attempts.
If I switch back to version 4.23.2 everything works as expected.
Additional information:
Os version: Ubuntu 22.04 Installation method: Deb package Apache Cassandra tested versions: 4.1.4, 5.0 Extension tested versions: 4.27,4.26,4.25 Liquibase tested versions: 4.27,4.26,4.25
Contents of my liquibase.properties file:
Output of
liquibase --version
: