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

Restart is not triggered at changes to init script or config #225

Open
solsson opened this issue Nov 28, 2018 · 2 comments
Open

Restart is not triggered at changes to init script or config #225

solsson opened this issue Nov 28, 2018 · 2 comments
Milestone

Comments

@solsson
Copy link
Contributor

solsson commented Nov 28, 2018

As a follow up from #55 (comment). After #55 you could be forgiven for thinking that an essential init script or broker.properties change is picked up automatically. We should also investigate if #224 is related.

@solsson
Copy link
Contributor Author

solsson commented Nov 28, 2018

Any ingenious solutions like the liveness probe idea in #55 (comment) must take into account that pods in a statefulset should never restart concurrently or when any other pod is unready.

@solsson
Copy link
Contributor Author

solsson commented Dec 2, 2018

When testing #228 (comment) I realized that having two statefulsets of zookeeper is quite useful when you need delete+apply ("updates to statefulset spec for fields other than 'replicas', 'template', and 'updateStrategy' are forbidden."). But also it makes rolling updates a bit risky.

The easiest way to do a rolling update now, or two, is to make a small change to a resource limit, such as +1 cpu, or edit a dummy env, then apply.

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

No branches or pull requests

1 participant