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
Making workflow engine truly stateless #225
Labels
Comments
The issue #226 is the first step in resolving this issue. We still need to change the code in honeydipper/drivers/cmd/redisqueue/main.go Lines 100 to 111 in ade16d7
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The workflow engine currently has an in memory data structure that holds all in-fly workflow sessions. We can't safely restart the daemon when there are workflows running. We have an issue to have a way to gracefully restart the daemon #190, but for a busy daemon, it will be challenging to find a window to do upgrade/maintenance etc.
The proposed solution is to persist the data into some kind of database such as consul, redis, memcached, couchdb etc. This way, we can safely/gracefully shutdown the daemon for upgrade or maintenance.
The text was updated successfully, but these errors were encountered: