Updates
amazon
- directory-reach-detector [before: 1.95.6.5][after: 1.95.6.9]
Notes
The only service update is directory-reach-detector to include the latest fixes for offline detection feature. This update pressuposes directory-reach-extractor to become non-relevant since all necessary actions in order to support offline detection will be handled by directory-reach-detector itself.
The most secure way to verify that everything is working as expected after the deployment is to run a new version in parallel with the old one. The only places where they can overlap are GlobalSubscribersReachListeners and subscribers-offline-package itself. In order to guarantee a sufficient level of isolation, a 1.95.6.9 version is shipped with a different prefix for global reach listener, so there should be no interference between those two ones. Overlapping writes to subscribers-offline-package should not be an issue, since both versions operate with the same data format.
Also, since a new offline-detection mechanism was never used in production before, it is advised to monitor it’s performance by checking logs. For that purpose, DEBUG level logging should be enabled by setting the following environment variable:
Potential risks
Even though deployment is marked as non-risky, there are still some potential risks to consider:
- increased Redis memory consumption due to keeping multiple compare slots for offline detection (each with it’s own window size)
- increased Redis CPU consumption due to the fact that we perform binary-map-to-ids conversion within Lua script running on Redis side
export DIRECTORY_DEBUG_MODE=1Post-deployment actions
- turn off directory-reach-extractor service in order to avoid unnecessary resource consumption
- turn off subscribers-updates service, since it is tightly coupled with directory-reach-extractor and is not needed anymore