Improve performance of Elasticsearch notes permissions migration
What does this MR do?
We are currently running this migration in production to reindex all the notes in GitLab.com. There happen to be over 30M of them so it will take quite a while to run. We have found in #324745 (closed) that the migration is not performing as well as we'd hoped. Given that we want to keep each job taking less than 1 minute to run we want to reduce the batch size to make that easier.
We have found that 9000 per 3 minutes is too much and we are regularly overlapping with the previous batch and thus we end up often processing the same batch twice.
In addition it will be more efficient to push the work into the "initial indexing queue" instead of our main "incremental indexing queue" as the initial indexing queue has far less traffic (it only covers newly created projects while incremental is any record update in any project).
Screenshots (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
📋 Does this MR need a changelog?-
I have included a changelog entry. -
I have not included a changelog entry because _____.
-
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team