-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Properties file entries for maximum resiliency #817
Comments
Not really - the original request was to make it resilient OOTB, which it clearly isn't. I don't think hiding this away in the docs is necessarily the best solution we can provide.... |
Gotcha - I mis-read the initial issue. |
Fixes confluentinc#817 - Adds new property file for production settings - Changes to allow topic prefixed streams configs such as min.insync.replicas - Unit tests added - Verfied locally that the property file, creates topics with correct configuration
Fixes confluentinc#817 - Adds new property file for production settings - Changes to allow topic prefixed streams configs such as min.insync.replicas - Unit tests added - Verfied locally that the property file, creates topics with correct configuration
Fixes confluentinc#817 - Adds new property file for production settings - Changes to allow topic prefixed streams configs such as min.insync.replicas - Unit tests added - Verfied locally that the property file, creates topics with correct configuration
Fixes confluentinc#817 - Adds new property file for production settings - Changes to allow topic prefixed streams configs such as min.insync.replicas - Unit tests added - Verfied locally that the property file, creates topics with correct configuration
Fixes confluentinc#817 - Adds new property file for production settings - Changes to allow topic prefixed streams configs such as min.insync.replicas - Unit tests added - Verfied locally that the property file, creates topics with correct configuration
Fixes #817 - Adds new property file for production settings - Changes to allow topic prefixed streams configs such as min.insync.replicas - Unit tests added - Verfied locally that the property file, creates topics with correct configuration
Recent enhancements to Kafka Streams API e.g KIP-224 have made it easier to configure a Streams application for maximum resiliency in the face of broker unavailability, such as that encountered during a rolling restart for example.
It seems desirable to collect all such best-practice settings and include them as defaults in the OOTB settings, or at the very least prominently document them.
For those users who prefer a 'fail-fast' approach, we can supply documentation of how to adjust the defaults to achieve this.
The text was updated successfully, but these errors were encountered: