Content
Updated by Markus Kahl 18 days ago
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><tbody><tr class="op-uc-table--row"><td class="op-uc-table--cell" style="vertical-align:bottom;"><p class="op-uc-p"></p></td><td class="op-uc-table--cell" style="text-align:center;vertical-align:bottom;"><p class="op-uc-p"><strong>Time (CEST/Berlin) on 24.04.2024</strong></p></td><td class="op-uc-table--cell" style="text-align:center;vertical-align:bottom;"><p class="op-uc-p"><strong>Duration</strong></p></td></tr><tr class="op-uc-table--row"><td class="op-uc-table--cell" style="vertical-align:bottom;"><p class="op-uc-p"><strong>all shards</strong></p></td><td class="op-uc-table--cell" style="vertical-align:bottom;"><p class="op-uc-p">7:00 – 8:00</p></td><td class="op-uc-table--cell" style="vertical-align:bottom;"><p class="op-uc-p">60min</p></td></tr></tbody></table></figure>
We deploy all shards at once. The approximate timings for migrations at most 10 minutes across all shards.
We will try to get the progress update background jobs done within the announced maintenance window. These take about 10 minutes for most shards, but around 30 minutes for vips1 and 2. Accordingly these have priority and should be deployed first.
**Plan**
1. Prebuild docker image (##54315)
2. Deploy first: vips1, vips2, vips3, bim-trials1 (DO NOT SKIP SCALING)
3. Enqueue next: trials1, trials2, trials3 (DO NOT SKIP SCALING)
We deploy all shards at once. The approximate timings for migrations at most 10 minutes across all shards.
We will try to get the progress update background jobs done within the announced maintenance window. These take about 10 minutes for most shards, but around 30 minutes for vips1 and 2. Accordingly these have priority and should be deployed first.
**Plan**
1. Prebuild docker image (##54315)
2. Deploy first: vips1, vips2, vips3, bim-trials1 (DO NOT SKIP SCALING)
3. Enqueue next: trials1, trials2, trials3 (DO NOT SKIP SCALING)