This deployment is a second and final part of the 2024.1.1 release.
Updates
manager API
- 1266 - base journey implementation
- 1276 - campaign statuses refactored
- 1257 - source activity reports
directory
- 1348 - this one is important. it reverts changes for source parameters and returns to using postgresql for storing them
Risks
- wrong statuses for campaigns might lead to stopped campaigns be still active
- source parameters table been deleted. to avoid that - please fake all new migrations before subscribers - 0065_auto_20240201_1706 - 0064_subscribersourceparameter
- callback processor will not be able to work quick enough with a source parameters enabled
Update plan
- mitigate a risk of stopped campaigns still running - https://push-service.atlassian.net/browse/PUSH-1339
- release update for all of directory services that use source-parameter entity
- update manager API
- update manager campaigns service
- update manager observer
- update manager database observer
- check and update campaign statuses
- clean old page view event (since they are not compatible with a new schema)
- there is a hypothesis that after a yesterday’s deployment we’re having a problem with source parameters for new users. needs to be checked
Update map
| service | before | after |
|---|---|---|
| directory-api | 1.63.7.1 | 1.64.0.1 |
| callback-processor | 1.63.7.1 | 1.64.0.1 |
| directory-messages | 1.63.7.1 | 1.64.2.1 |
| subscribers-cache | 1.56.4.1 | 1.64.0.1 |
| subscribers-tasks | 1.63.11.1 | 1.64.0.1 |
| subscribers-postponed | 1.63.7.1 | 1.64.0.1 |
| subscribers-errors | 1.63.7.1 | 1.64.3.1 |
| manager-api | 1.93.24.2 | 1.96.9.1 |
| manager | 1.93.22.2 | 1.96.9.1 |
| manager-observer | 1.93.19.1 | 1.96.9.1 |
| manager-database-updates | 1.93.19.1 | 1.96.9.1 |
Problems during deployment
- manager had been affected with a deployment by dramatically increasing a CPU load. rollback to 1.93.22.2 helped but the origin of the problem is still to be found
Links
-
affected: