4

We have a deployment slot that we deploy to, which we then warm up, and then swap with the live slot so that we can achieve zero downtime deployment on PaaS. This works very well in general.

However, we are noticing an issue where both of the slots appear to be responding to the event queue and processing things like item:saved events and updating the indexes and weird things are happening like duplicate documents ending up in the index.

Currently, it seems like the best option is to be very diligent about stopping the staging slot and then rebuilding the indexes once the staging slot is turned off.

Has anyone dealt with this issue before?

  • It is very hard to do zero downtime for CM. Content freeze is still required to get around this problem. Have a look at this blog post robhabraken.nl/index.php/2683/the-staging-slot-eventqueue-issue – Vincent Lui Nov 12 '19 at 19:04
  • 1
    My general recommendation is to not keep the CM staging slot running long enough to have this problem. i.e. deploy and swap the slot and then stop the old one as soon as possible. It seems to work fine for all the installs I've done. – Mark Gibbons Nov 12 '19 at 22:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.