You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The issue #226 is the first step in resolving this issue. We still need to change the code in internal/workflow to use the cache, and the communication between the workflow engine and operator needs to be node neutral (currently, we use engine IP to identify the node of the engine like below.)
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: