MirrorMirror
/
Signal-Server
mirror of https://github.com/signalapp/Signal-Server.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Revert "Restore max concurrency when migrating pre-keys" 

This reverts commit ed8a1ed579.
This commit is contained in:
Jon Chambers 2023-07-26 12:56:35 -04:00
parent ed8a1ed579
commit e1a5105c28
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
service/src/main/java/org/whispersystems/textsecuregcm/workers/MigrateSignedECPreKeysCommand.java
View File

@ -26,11 +26,9 @@ public class MigrateSignedECPreKeysCommand extends AbstractSinglePassCrawlAccoun
private static final String STORE_KEY_ATTEMPT_COUNTER_NAME =
MetricsUtil.name(MigrateSignedECPreKeysCommand.class, "storeKeyAttempt");
// It's tricky to find, but this is the default connection count for the AWS SDK's async DynamoDB client. We'll have
// multiple workers using the max number of connections, but that's okay because the client allows for (by default)
// 10,000 pending requests. As long as we don't have more than 200(!) workers, we'll be fine with this concurrency
// level.
private static final int MAX_CONCURRENCY = 50;
// It's tricky to find, but the default connection count for the AWS SDK's async DynamoDB client is 50. We expect
// four workers, so this should keep us below the concurrency limit.
private static final int MAX_CONCURRENCY = 12;
public MigrateSignedECPreKeysCommand() {
super("migrate-signed-ec-pre-keys", "Migrate signed EC pre-keys from Account records to a dedicated table");