Skip to content

Inconsistent cached configuration after failed refreshAll operations #178

Description

@abhilasharora

When a change is detected in a sentinel key-value with refreshAll set to true, a refreshAll operation is triggered to populate the entire configuration from scratch. However, in case we fail to complete that operation and all retry attempts fail, the subsequent calls to TryRefreshAsync fail to detect changes and do not attempt to retry the failed operation. This issue tracks the changes required to ensure that failed refreshAll operations do not leave the internal configuration cache in an inconsistent state.

Metadata

Metadata

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions