-
Notifications
You must be signed in to change notification settings - Fork 467
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fixing IOPs issue with lease table #360
Conversation
* Making DynamoDBLeaseCoordinator take IOPs configuration in the constructor * InitialLeaseTableReadCapacity and InitialLeaseTableWriteCapacity for the DynamoDBLeaseCoordinator class throws UnsupportedException
} | ||
this.initialLeaseTableReadCapacity = readCapacity; | ||
return this; | ||
throw new UnsupportedOperationException("Please set read capacity using the constructor"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking change. Keep the setting available. You can mark them as deprecated though.
@@ -100,6 +110,8 @@ public DynamoDBLeaseCoordinator(final LeaseRefresher leaseRefresher, | |||
final int maxLeasesForWorker, | |||
final int maxLeasesToStealAtOneTime, | |||
final int maxLeaseRenewerThreadCount, | |||
final long initialLeaseTableReadCapacity, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we just added the @KinesisClientInternalApi
retain the existing constructor and chain them together. You can mark the original constructor as deprecated.
* Reverting the constructor, and adding chained constructor * Reverting support for initial iops methods * Adding deprecated tags and notes to javadoc
* Introducing chained constructors in DynamoDBLeaseManagementFactory * Introducing TableConstants to maintain Default IOPS in one place
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.