Skip to content

Increase GSI creation timeout - #1786

Merged
lucienlu-aws merged 1 commit into
awslabs:masterfrom
lucienlu-aws:gsi-timeout
Jul 9, 2026
Merged

lucienlu-aws merged 1 commit into
awslabs:masterfrom
lucienlu-aws:gsi-timeout

Conversation

@lucienlu-aws

@lucienlu-aws lucienlu-aws commented Jul 9, 2026 •

Copy link
Copy Markdown
Contributor

Issue #, if available:

Description of changes:
Recent changes to move all DDB entities to the lease table appear to have increased the time it takes for a new KCL application to create the GSI. Increase the timeout within the KCL to 30 minutes and increase the timeout for the integration test.

Example integ test run: https://github.com/awslabs/amazon-kinesis-client/actions/runs/27999135345/job/82867500158

2026-06-23 03:13:29,060 [pool-12-thread-1] INFO  s.a.k.l.d.DynamoDBLeaseRefresher [NONE] - GSI status was not active, after 600s 

From local testing this can take around 15-20 minutes now. Validated workflow in fork https://github.com/lucienlu-aws/amazon-kinesis-client/actions/runs/29048851719/job/86224205547

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

@lucienlu-aws

Copy link
Copy Markdown
Contributor Author

Overriding integ test timeout since the workflow file doesn't update until it reaches master branch

@lucienlu-aws
lucienlu-aws merged commit 7c747fa into awslabs:master Jul 9, 2026
6 of 7 checks passed

This branch was previously deployed

1 inactive deployment
manual-approval β€” 6da2f23c Deployed Jul 9, 2026 by lucienlu-aws via wait-for-approval #270
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.

2 participants