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

Handler: systemd service no_block restart configurable? #402

Open
msegura501 opened this issue Jan 11, 2024 · 0 comments · May be fixed by #404
Open

Handler: systemd service no_block restart configurable? #402

msegura501 opened this issue Jan 11, 2024 · 0 comments · May be fixed by #404

Comments

@msegura501
Copy link
Contributor

The handler is restarting nexus with no_block: true. Waiting for a healthy completed restart is done by the handler a little bit later in the handler by searching for string "Wait for Nexus to start" in the nexus log (here).

This is not ideal in upgrade scenarios where nexus has been restarted recently (the log may already contain the Started Sonatype Nexus) and Wait for Nexus port to be available can be reached before the restart has actually taken place.

Would it be ok to make the no_block configurable so that it can be disabled when there is a risk ?

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

Successfully merging a pull request may close this issue.

1 participant