Overview
This deployment is aimed to introduce dynamic segments for the following events:
awake- when the user comes back to the channel after a long time (after being registered as offline by offline-detection)clicks- when the user clicks on a notificationofflines- when the user is registered as offline by offline-detection
Since there are a lot of affected components that should be updated, this deployment is marked as risky. Updates will be applied on both: master (amazon) and on-prems clusters (senders)
Pre-deployment steps
- start directory (1.93.2.0) and manager (1.123.0.0) instances on amazon for migration purposes
- grab pending database migrations, analyze them, find potential risks if any
Updates
amazon
- manager-api [before: 1.122.19.0][after: 1.123.0.0]
- manager-observer [before: 1.113.18.3][after: 1.123.0.0]
- directory-segments-observer [before: 1.89.6.0][after: 1.93.2.0]
- directory-subscribers-data [before: 1.89.14.0][after: 1.93.2.0]
- subscribers-cache [before: 1.89.14.0][after: 1.93.2.0]
- directory-awake-detection [before: 1.88.4.0][after: 1.93.2.0]
on-premises
- directory-subscribers-data [before: 1.89.14.0][after: 1.93.2.0]
- directory-messages [before: 1.89.21.0][after: 1.93.2.0]
- directory-server [before: 1.89.14.0][after: 1.93.2.0]
- subscribers-cache [before: 1.89.14.0][after: 1.93.2.0]
- manager [before: 1.121.7.0][after: 1.123.0.0]
- manager-database-updates [before: 1.121.17.0][after: 1.123.0.0]
- manager-consumer [before: 1.121.7.0][after: 1.123.0.0]
Post-deployment steps
- verify that offline detection works on Amazon (offline users should be registered within subscribers-offline-package)
- check that offline detection does not skip any messages while sending them (directory-messages)
- check that directory-awake-detection works as expected (it should register users as awake after they come back to the channel. such events should be visible in logs)
- make tests for all types of segments