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

Persistent topology monitor to ensure uptime of submitted topologies. #40

Open
juliencruz opened this issue Aug 30, 2015 · 0 comments
Open
Assignees
Milestone

Comments

@juliencruz
Copy link
Contributor

Currently, when a topology is submitted by a user from streamflow there are no protections that it will continue to run if there is a cluster outage.

This feature should implement a persistent service within the streamflow server that ensures that a topology that has been submitted will be resubmitted if the topology goes down for any reason. This will improve topology uptime in the event that a storm cluster goes down and comes back up for any reason.

Once a user triggers the kill operation in streamflow, the topology will be flagged as killed and should no longer be auto deployed.

The streamflow configuration should allow for enabling/disabling of this feature and controlling the polling interval of the service. A suggested config format is as follows:

monitor:
    enabled: true
    pollingInterval: 60
@juliencruz juliencruz self-assigned this Aug 30, 2015
@juliencruz juliencruz added this to the 0.13 milestone Aug 30, 2015
juliencruz added a commit to juliencruz/streamflow that referenced this issue Aug 30, 2015
…s to ensure they stay up even after a cluster outage.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant