Is it possible to do a live upgrade where we update the database schema while old version of Activiti is running?
Our application runs in a complex environment with many servers and we have a requirement where we can not shutdown the entire cluster at the same time to perform and upgrade.
So are the database upgrades normally backwards compatible? I know activity has a schema check which is what prompted this question.
Normally we direct traffic off some of our clusters and then shutdown our applications to apply db changes and upgraded software. Then we bring up the upgraded machines and repeat on the next. Currently we have all instances running on the same database and now we are evaluating what are the options for future upgrades.
Does the engine support this? Ideally we would like to just divert traffic, allow current processes to get to a hold/completed state, shutdown applications, apply db upgrades, upgrade Activiti jars, bring back up, then repeat on the other nodes (skipping the db upgrade as it was already performed).
Thanks
