[
https://issues.apache.org/jira/browse/CASSSIDECAR-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSSIDECAR-434:
------------------------------------
Authors: Paulo Motta
Test and Documentation Plan: unit tests
Status: Patch Available (was: Open)
> Implement failure policies for ConfigurationProvider unavailability
> -------------------------------------------------------------------
>
> Key: CASSSIDECAR-434
> URL: https://issues.apache.org/jira/browse/CASSSIDECAR-434
> Project: Sidecar for Apache Cassandra
> Issue Type: Task
> Components: Configuration
> Reporter: Paulo Motta
> Priority: Major
>
> CEP-62 defines three failure policies that govern Configuration Manager
> behavior when the \{{ConfigurationProvider}} is unreachable or fails. The
> \{{failure_policy}} setting in \{{sidecar.yaml}} determines how
> initialization, read operations, and updates behave:
> - \{{CACHED_READ_WRITE}}: All operations fall back to cached configuration.
> Reads use cache, updates are applied to cached overlay.
> - \{{CACHED_READ_ONLY}} (default): Reads fall back to cache, updates are
> rejected.
> - \{{FAIL}}: All operations fail.
> Acceptance Criteria:
> - Configuration Manager respects the configured failure policy when the
> \{{ConfigurationProvider}} is unavailable.
> - \{{CACHED_READ_WRITE}}: Initialization, reads, and updates all fall back to
> cached configuration.
> - \{{CACHED_READ_ONLY}}: Initialization and reads fall back to cache; updates
> are rejected.
> - \{{FAIL}}: Initialization, reads, and updates all fail.
> - \{{failure_policy}} is configurable in \{{sidecar.yaml}} with
> \{{CACHED_READ_ONLY}} as default.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
