Details
-
Dependency upgrade
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Currently when a new version of storm is released in order to upgrade existing storm clusters users need to backup their existing topologies , kill all the topologies , perform the upgrade and resubmit all the topologies. This is painful and results in downtime which may not be acceptable for "Always alive" production systems.
Storm should support a rolling upgrade/downgrade deployment process to avoid these downtimes and to make the transition to a different version effortless.
Based on my initial attempt the primary issue seem to be the java serialization used to serialize java classes like StormBase, Assignment, WorkerHeartbeat which is then stored in zookeeper. When deserializing if the serial versions do not match the deserialization fails resulting in processes just getting killed indefinitely. We need to change the Utils/serialize and Utils/deserialize so it can support non java serialization mechanism like json.
Attachments
Issue Links
- links to
