Temporary outage for Exalate nodes

RCA and Postmortem to follow

During the outage, some sync events could be missed. To recover the missed sync events, please follow the next steps:

1. Create a search query that would contain the existing trigger query (if available) + the update date being between "2023-05-23 9:21" and time of the outage resolution "2023-05-23 12:23"
2. Find how many issues were affected.
3. Split the results into batches of 100 (500 for EPSO customers) by limiting the query results by issue key numbers being between given bounds or ticket creation date being between given bounds.
4. For every batch create a disabled trigger.
5. Run Bulk Exalate on one of the triggers, as soon as the sync queue is empty, repeat the step for other disabled triggers from step 4.

The fix has been deployed and the infrastructure has been restarted. We are monitoring the infrastructure.

The database is restarted.

A critical issue Has been raised with Google cloud.

Exalate infrastructure experienced a DB restart. The reason of the restart is under investigation.
We are applying a fix on all Exalate instances.
All Exalate nodes will be down during this process.