ROX-30961: simplify to single thread#17049
Conversation
|
This change is part of the following stack: Change managed by git-spice. |
|
Images are ready for the commit at b2f3c17. To use with deploy scripts, first |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #17049 +/- ##
==========================================
+ Coverage 48.80% 48.81% +0.01%
==========================================
Files 2706 2716 +10
Lines 202090 202346 +256
==========================================
+ Hits 98631 98778 +147
- Misses 95695 95789 +94
- Partials 7764 7779 +15
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
/retest |
|
Caution There are some errors in your PipelineRun template.
|
|
@dashrews78: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Description
Competitor to #16935 which does the migration sequentially instead of concurrently. On the other one encountering some race conditions in pgx. Need to go through all process indicators which could be large. Grabbing and batching them by cluster seemed like a reasonable choice. This is single threaded, the real thought behind getting them by cluster was to run some of the updates concurrently.
Ran a cluster with 11M indicators across 7 clusters. The migration took 15 minutes.
User-facing documentation
Testing and quality
Automated testing
How I validated my change
Unit test, upgrade test, and local test with around 7 clusters and 11M process indicators.