Increase the cluster creation timeout to 24 hours #123
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the documentation, Confluent states that dedicated clusters can take up to 24 hours to provision on AWS.
|
We are using this provider to deploy production clusters in confluent cloud. Our deployment pipeline is going to be impacted by this timeout. This simple change will make our deployment process so much streamlined. |
borisnaydis
deleted the
borisnaydis-increase-kafka-cluster-creation-timeout-to-24h
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the documentation, Confluent states that dedicated clusters can take up to 24 hours to provision on AWS.
The current timeout value of 20 minutes is not enough for a Dedicated cluster even with 2 CKUs, which takes 2+ hours across all supported service providers.
This change increases the timeout to 24 hours to accommodate for this.