Skip to content
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

DDB is considered healthy in UPDATING status #725

Merged
merged 1 commit into from
Jun 24, 2020

Conversation

Cai41
Copy link
Contributor

@Cai41 Cai41 commented Jun 5, 2020

Description of changes:
Based on: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/WorkingWithTables.Basics.html#WorkingWithTables.Basics.UpdateTable

When you issue an UpdateTable request, the status of the table changes from AVAILABLE to UPDATING. The table remains fully available for use while it is UPDATING. When this process is completed, the table status changes from UPDATING to AVAILABLE.

If we are updating a table's IOPS or billing mode, the UPDATING status can remain few minutes to one hour. This prevents KCL thread from starting. However based on DDB documentation, it is still functioning during UPDATING process, so KCL thread should be able to continue in this situation.

mvn clean install -DskipITs passed.

Note : This change is the same as the pull request in v1.x branch: #712

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@Cory-Bradshaw
Copy link
Contributor

Change looks good to me. Thanks for helping keep the KCL versions at parity here.

@Cory-Bradshaw Cory-Bradshaw merged commit 8767725 into awslabs:master Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants