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

upload jar before killing existing topology #277

Merged
merged 1 commit into from
Jul 19, 2016

Conversation

emmettbutler
Copy link
Contributor

if we kill the topology before uploading the jar, the topology stays disabled until the upload is complete. on a slow network, this can lead to the topology being disabled for an unacceptably long time during the deployment. additionally, if the upload fails and deployment crashes, this change will ensure that it did not have a destructive effect on the existing topology.

if we kill the topology before uploading the jar, the topology stays disabled until the upload is complete. on a slow network, this can lead to the topology being disabled for an unacceptably long time during the deployment. additionally, if the upload fails and deployment crashes, this change will ensure that it did not have a destructive effect on the existing topology.
@dan-blanchard
Copy link
Member

Thanks for the great simpler PR. This will be a big win on slow connections, like you said.

@dan-blanchard dan-blanchard merged commit 552c344 into master Jul 19, 2016
@dan-blanchard dan-blanchard deleted the feature/deploy_order branch July 19, 2016 15:12
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 this pull request may close these issues.

2 participants