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

Improve first installation playbook to not use serial #13

Closed
guidograzioli opened this issue Feb 24, 2022 · 0 comments · Fixed by #17
Closed

Improve first installation playbook to not use serial #13

guidograzioli opened this issue Feb 24, 2022 · 0 comments · Fixed by #17
Assignees
Labels
enhancement New feature or request

Comments

@guidograzioli
Copy link
Member

When a cluster of keycloaks is installed for the first time, liquibase needs to be run for initializing the database.
Even if a dblock is in the jpa configuration, the nodes of clusters that are started at the same time, concurrently
try to perform the database update, resulting in errors. Current workaround is to have playbook run with

serial:
  - 1
  - 100%

which will run the full playbook on the first host, and then run again on remaining nodes.

Improvement is needed to check database state before starting the service, and in case an update is needed,
only serialize the startup of instances (along with the wait task to let the database update terminate), not the whole play.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant