Split liquibase changeset of HTextFlowTarget and History #827
Conversation
<changeSetExecuted id="3" author="aeng@redhat.com" changeLogFile="db/changelogs/db.changelog-3.7.xml"/> | ||
</not> | ||
</preConditions> | ||
<comment>Add revisionComment HTextFlowTargetHistory</comment> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You accidentally a word.
👍 |
❌ Cannot merge |
release notes... |
@zanata-jenkins retest this please |
@definite Did you increase the deployment timeout as in the release notes? Mysqld should eventually have finished off the DBML operation it was on. (I usually watch the I/O stats to see when that is, but I think you should be able to tell from mysql's log file.) You'll need to remove the dbchangeloglock, but the singular changeset should make the recovery a lot simpler than it would be otherwise. Zanata should then be able to pick up at the next changeset. |
@definite I think the imported database has some record in DATABASECHANGELOGLOCK. If you've only run once as suggested in the log, then, remove all record in DATABASECHANGELOGLOCK table and startup Zanata again. |
@zanata-jenkins retest this please |
16:35:25,825 INFO [liquibase](ServerService Thread Pool -- 63) db/db.changelog.xml: db/changelogs/db.changelog-3.7.xml::3-split::aeng@redhat.com: ChangeSet db/changelogs/db.changelog-3.7.xml::3-split::aeng@redhat.com ran successfully in 4235350ms More than 70 mins on my machine. |
Merged into integration/master. 6c19620 |
https://bugzilla.redhat.com/show_bug.cgi?id=1207980