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.

Sign up for GitHub

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

Jump to bottom

don't block handler during initial config #64

Closed
joel-bluedata opened this issue Oct 5, 2018 · 0 comments
Closed

don't block handler during initial config #64

joel-bluedata opened this issue Oct 5, 2018 · 0 comments
Assignees
@joel-bluedata
Labels
Priority: High Project: Cluster Reconcile beyond simple xlate of model to K8s spec Type: Enhancement
Milestone
0.2.0

Comments

@joel-bluedata
Copy link
Member

We shouldn't run an initial startscript invocation synchronously. Not only would a super-long (or indefinite) startscript block deletion of the cluster, it can also cause potential setup deadlock issues as described in issue #54 if the startscripts on different members try to coordinate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@joel-bluedata joel-bluedata

Labels
Priority: High Project: Cluster Reconcile beyond simple xlate of model to K8s spec Type: Enhancement
Projects
None yet
Milestone
0.2.0
Development

No branches or pull requests
1 participant
@joel-bluedata